Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbc0cf21ff7c04e29e83ff6b62f66ab71c701d6e14b15b34e265e61da6c6404a

Tx prefix hash: cfa54d71766c6169848748c62b9835bd7fb1d7c5e521f856ba4e5b55dc498899
Tx public key: 4759424d609fad5e6b364b68f75a6e6b3ae8d34d5ab4b58a306ddaec26792659
Timestamp: 1723403263 Timestamp [UCT]: 2024-08-11 19:07:43 Age [y:d:h:m:s]: 00:290:12:37:09
Block: 1085761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207582 RingCT/type: yes/0
Extra: 014759424d609fad5e6b364b68f75a6e6b3ae8d34d5ab4b58a306ddaec2679265902110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c70aa6b404894326b00e2a1128084749cf7acd7adb4675509623a7510113d0c 0.600000000000 1560350 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": 1085771, "vin": [ { "gen": { "height": 1085761 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c70aa6b404894326b00e2a1128084749cf7acd7adb4675509623a7510113d0c" } } ], "extra": [ 1, 71, 89, 66, 77, 96, 159, 173, 94, 107, 54, 75, 104, 247, 90, 110, 107, 58, 232, 211, 77, 90, 180, 181, 138, 48, 109, 218, 236, 38, 121, 38, 89, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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