Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a52f5c9e12ad8fd1b79fd5cbfe6f727b97f4179ff3f5cde34ad6ee3aa33477c

Tx prefix hash: f380fd0add8a3b1d4560f59df0592d0bcf6e4fdb329cd6cff61ff3d3b894b747
Tx public key: af90dc217dece8da22d3be8ea57bd5bde59631d489dc68bab943d15df1b746e2
Timestamp: 1719015665 Timestamp [UCT]: 2024-06-22 00:21:05 Age [y:d:h:m:s]: 00:293:18:38:51
Block: 1049381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209948 RingCT/type: yes/0
Extra: 01af90dc217dece8da22d3be8ea57bd5bde59631d489dc68bab943d15df1b746e202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7167589a454cf009b3650b112d63339913af322f3bb1a39f8cbb29c292344e96 0.600000000000 1519480 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": 1049391, "vin": [ { "gen": { "height": 1049381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7167589a454cf009b3650b112d63339913af322f3bb1a39f8cbb29c292344e96" } } ], "extra": [ 1, 175, 144, 220, 33, 125, 236, 232, 218, 34, 211, 190, 142, 165, 123, 213, 189, 229, 150, 49, 212, 137, 220, 104, 186, 185, 67, 209, 93, 241, 183, 70, 226, 2, 17, 0, 0, 0, 1, 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