Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 646478da0d9dd10de694c934a564b52643826098c9c83861d7176a924dbb1828

Tx prefix hash: 8b1b9189aa17c36b1cd7c5c4995a6d0ce6625e81033a47aab677e82817706dfc
Tx public key: 1b949a24582c6ae569efffc5fa4babecceafeb3436995ffe08147d4a617d511e
Timestamp: 1582051090 Timestamp [UCT]: 2020-02-18 18:38:10 Age [y:d:h:m:s]: 04:310:18:15:27
Block: 67692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1114479 RingCT/type: yes/0
Extra: 011b949a24582c6ae569efffc5fa4babecceafeb3436995ffe08147d4a617d511e02110000000c8a2ee0d9000000000000000000

1 output(s) for total of 366.192217968000 dcy

stealth address amount amount idx
00: 13f6c9d713bee83349571e7f71ccf2a29c1dccb53392412a11f05aa54037257b 366.192217968000 124671 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": 67702, "vin": [ { "gen": { "height": 67692 } } ], "vout": [ { "amount": 366192217968, "target": { "key": "13f6c9d713bee83349571e7f71ccf2a29c1dccb53392412a11f05aa54037257b" } } ], "extra": [ 1, 27, 148, 154, 36, 88, 44, 106, 229, 105, 239, 255, 197, 250, 75, 171, 236, 206, 175, 235, 52, 54, 153, 95, 254, 8, 20, 125, 74, 97, 125, 81, 30, 2, 17, 0, 0, 0, 12, 138, 46, 224, 217, 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