Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b40b46cd10e61d76fdc8571f39bbc10a2805dbdd2407b681cf38b13e67837d4

Tx prefix hash: 0d1c1f2e895668022ed5a993501a1650662d831e3e517bc7ab0f224eca458406
Tx public key: c8dfeb4292ad56f939005f8aeb9435701b78383ed3b6bb631e97e00019aa8ae7
Timestamp: 1708998874 Timestamp [UCT]: 2024-02-27 01:54:34 Age [y:d:h:m:s]: 01:071:10:42:33
Block: 966362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312086 RingCT/type: yes/0
Extra: 01c8dfeb4292ad56f939005f8aeb9435701b78383ed3b6bb631e97e00019aa8ae702110000000f52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cab7592967fb7dfdca55c1e42406e8dc40ce523c0d4bcb192fdc2daf8691e720 0.600000000000 1426119 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": 966372, "vin": [ { "gen": { "height": 966362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cab7592967fb7dfdca55c1e42406e8dc40ce523c0d4bcb192fdc2daf8691e720" } } ], "extra": [ 1, 200, 223, 235, 66, 146, 173, 86, 249, 57, 0, 95, 138, 235, 148, 53, 112, 27, 120, 56, 62, 211, 182, 187, 99, 30, 151, 224, 0, 25, 170, 138, 231, 2, 17, 0, 0, 0, 15, 82, 212, 126, 148, 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