Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7210d865320d5c03d287ad96f892fe38674be5109e908b28a8ea5816362e3d1

Tx prefix hash: a85f4bedc49491996779070e05e1f3cddb6b07752e07830a68eb5c8a944f24dd
Tx public key: eef4054fb549fa97e988f54a7ee6f2cb2e370095b903314232e8f481b396484e
Timestamp: 1706651405 Timestamp [UCT]: 2024-01-30 21:50:05 Age [y:d:h:m:s]: 01:284:18:45:29
Block: 946871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462332 RingCT/type: yes/0
Extra: 01eef4054fb549fa97e988f54a7ee6f2cb2e370095b903314232e8f481b396484e0211000000060011055b000000000000000000

1 output(s) for total of 0.600030000000 dcy

stealth address amount amount idx
00: 437defb4a7ad539f3a14c38a4453400be4f718c953feb0721fef5b85282a0a72 0.600030000000 1405211 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": 946881, "vin": [ { "gen": { "height": 946871 } } ], "vout": [ { "amount": 600030000, "target": { "key": "437defb4a7ad539f3a14c38a4453400be4f718c953feb0721fef5b85282a0a72" } } ], "extra": [ 1, 238, 244, 5, 79, 181, 73, 250, 151, 233, 136, 245, 74, 126, 230, 242, 203, 46, 55, 0, 149, 185, 3, 49, 66, 50, 232, 244, 129, 179, 150, 72, 78, 2, 17, 0, 0, 0, 6, 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