Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0a527082cb4a1516d405a120dc4a47c02f96032476053afa480b9e255c4d6ede

Tx prefix hash: 8fb3dcad2db6bfde72732da5591d3cb640425147311f6d142d59e66fbe3b376e
Tx public key: f7e89a49e222ef32055324f7334d92ce9e178332f356cefd36389b32e692415d
Timestamp: 1578442201 Timestamp [UCT]: 2020-01-08 00:10:01 Age [y:d:h:m:s]: 05:034:00:14:00
Block: 40871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1174279 RingCT/type: yes/0
Extra: 01f7e89a49e222ef32055324f7334d92ce9e178332f356cefd36389b32e692415d02110000000bd81c26c0000000000000000000

1 output(s) for total of 449.343286069000 dcy

stealth address amount amount idx
00: 59fc4990f20d5a403a2dc628e1dc041ab219b711f1727b79b05fc86fcb5c6493 449.343286069000 72236 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 40881, "vin": [ { "gen": { "height": 40871 } } ], "vout": [ { "amount": 449343286069, "target": { "key": "59fc4990f20d5a403a2dc628e1dc041ab219b711f1727b79b05fc86fcb5c6493" } } ], "extra": [ 1, 247, 232, 154, 73, 226, 34, 239, 50, 5, 83, 36, 247, 51, 77, 146, 206, 158, 23, 131, 50, 243, 86, 206, 253, 54, 56, 155, 50, 230, 146, 65, 93, 2, 17, 0, 0, 0, 11, 216, 28, 38, 192, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8