Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abcbd326bb8baa73e94e6b4b375e50c0e6560080d410eec80a94bc550b323313

Tx prefix hash: fed1bd5105e4bd419a745a0b54a02fe7a6a82a5074c3944aa9271a1929a72d7e
Tx public key: 72e03780e43410185213c70e6441f2b399980f8c3ea24e6ffcd67a278c7669cb
Timestamp: 1709190674 Timestamp [UCT]: 2024-02-29 07:11:14 Age [y:d:h:m:s]: 00:304:03:51:11
Block: 967951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217728 RingCT/type: yes/0
Extra: 0172e03780e43410185213c70e6441f2b399980f8c3ea24e6ffcd67a278c7669cb0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e3ae6d030a79bf7c66f7e1132e0e6c615b43747a5c464a11b000175d5354417 0.600000000000 1427746 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": 967961, "vin": [ { "gen": { "height": 967951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e3ae6d030a79bf7c66f7e1132e0e6c615b43747a5c464a11b000175d5354417" } } ], "extra": [ 1, 114, 224, 55, 128, 228, 52, 16, 24, 82, 19, 199, 14, 100, 65, 242, 179, 153, 152, 15, 140, 62, 162, 78, 111, 252, 214, 122, 39, 140, 118, 105, 203, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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