Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3132fead795dd6c03b10b9743244ac48350d3887686dca9b6ef5aa8c80fa40de

Tx prefix hash: 385f3f7cf420dd80c4ea8e4f293e3c2d79aee95c384e86dd24259b8faaf28d6b
Tx public key: ebcb1fd447b115ec1efc1534627b172902bc250d77d40172c79db69d4fb5ea0d
Timestamp: 1710681986 Timestamp [UCT]: 2024-03-17 13:26:26 Age [y:d:h:m:s]: 01:093:10:29:18
Block: 980331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327645 RingCT/type: yes/0
Extra: 01ebcb1fd447b115ec1efc1534627b172902bc250d77d40172c79db69d4fb5ea0d0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98ffb6aee1930b9277b80996b52802aacb1ae8b809a5acedd1079cba383270cc 0.600000000000 1440396 of 15

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": 980341, "vin": [ { "gen": { "height": 980331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98ffb6aee1930b9277b80996b52802aacb1ae8b809a5acedd1079cba383270cc" } } ], "extra": [ 1, 235, 203, 31, 212, 71, 177, 21, 236, 30, 252, 21, 52, 98, 123, 23, 41, 2, 188, 37, 13, 119, 212, 1, 114, 199, 157, 182, 157, 79, 181, 234, 13, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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