Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ad1122bfb6fd616481795be083a63b3f419b170d101a006f9c263ba20d98f45

Tx prefix hash: 9995ccf423c7dea37488810a17cc33dbf219f3879d65122c4f611e123c0644b2
Tx public key: c72b98af3b77da058563460881dc45f77c8c189e9b5b3309b711dc1d7bd3a59c
Timestamp: 1717560171 Timestamp [UCT]: 2024-06-05 04:02:51 Age [y:d:h:m:s]: 00:298:22:44:31
Block: 1037335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213633 RingCT/type: yes/0
Extra: 01c72b98af3b77da058563460881dc45f77c8c189e9b5b3309b711dc1d7bd3a59c02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc5fa615626637aa56778cd91567d3d64919c0cd8eea7f0be514afffc3dcf0f4 0.600000000000 1505866 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": 1037345, "vin": [ { "gen": { "height": 1037335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc5fa615626637aa56778cd91567d3d64919c0cd8eea7f0be514afffc3dcf0f4" } } ], "extra": [ 1, 199, 43, 152, 175, 59, 119, 218, 5, 133, 99, 70, 8, 129, 220, 69, 247, 124, 140, 24, 158, 155, 91, 51, 9, 183, 17, 220, 29, 123, 211, 165, 156, 2, 17, 0, 0, 0, 4, 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