Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23251d0c04e94cf5c9b5c4d22131effecb84fc01d821dad6e0734c3a242e13b6

Tx prefix hash: 84bc52a97658e3eac855215597f0040c1ee14234a23982d01483a7b46b54ebb9
Tx public key: 148c5192ddfeff32b0d8aaf62fb8f95d95d6c3d9a0ae3d3821ed66be6382881f
Timestamp: 1718704454 Timestamp [UCT]: 2024-06-18 09:54:14 Age [y:d:h:m:s]: 01:203:02:53:30
Block: 1046822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403804 RingCT/type: yes/0
Extra: 01148c5192ddfeff32b0d8aaf62fb8f95d95d6c3d9a0ae3d3821ed66be6382881f02110000000e59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9943600a102a25b4ef99287f449132bd97e6cf1d3ca45e6d0ecb73f5603277d9 0.600000000000 1516641 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": 1046832, "vin": [ { "gen": { "height": 1046822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9943600a102a25b4ef99287f449132bd97e6cf1d3ca45e6d0ecb73f5603277d9" } } ], "extra": [ 1, 20, 140, 81, 146, 221, 254, 255, 50, 176, 216, 170, 246, 47, 184, 249, 93, 149, 214, 195, 217, 160, 174, 61, 56, 33, 237, 102, 190, 99, 130, 136, 31, 2, 17, 0, 0, 0, 14, 89, 218, 211, 245, 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