Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5660a7eba8bc083bb83b68fd3dc1a24521098396a015489571340e2f282cce37

Tx prefix hash: 4b8952313f62fde855b36d55bea5ed5c8673c3e01e3a1080d1cd28b32c859a70
Tx public key: 3c4a83900087e0b54e8d5b2339d30e4256ce9f713aabd7434e0f00e00ae9bd0e
Timestamp: 1703807705 Timestamp [UCT]: 2023-12-28 23:55:05 Age [y:d:h:m:s]: 01:359:05:51:09
Block: 923314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515633 RingCT/type: yes/0
Extra: 013c4a83900087e0b54e8d5b2339d30e4256ce9f713aabd7434e0f00e00ae9bd0e0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fd61ae115e92cd3dcb2e08f7713044c0ded99774fc56f813f73611fc81cc65e 0.600000000000 1381042 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": 923324, "vin": [ { "gen": { "height": 923314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fd61ae115e92cd3dcb2e08f7713044c0ded99774fc56f813f73611fc81cc65e" } } ], "extra": [ 1, 60, 74, 131, 144, 0, 135, 224, 181, 78, 141, 91, 35, 57, 211, 14, 66, 86, 206, 159, 113, 58, 171, 215, 67, 78, 15, 0, 224, 10, 233, 189, 14, 2, 17, 0, 0, 0, 3, 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