Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bddf6c0feec19bc9ec33c551d7970d42469fb6fa2ba22cebbefd24053936146b

Tx prefix hash: 6d09c23101dd71bab3c900763a99209f861e3f612c7f73fd6ef4a5a79a401f7e
Tx public key: f6204dc6c5cae366d1853be823e58b5a569d68626b860096efda8a09f66d0db7
Timestamp: 1723207718 Timestamp [UCT]: 2024-08-09 12:48:38 Age [y:d:h:m:s]: 00:287:21:09:19
Block: 1084147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205678 RingCT/type: yes/0
Extra: 01f6204dc6c5cae366d1853be823e58b5a569d68626b860096efda8a09f66d0db702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64f97d5ea89133a95dcfd9b27f0a0e4d646fecbeb3a2167ccf619836fa2a0c91 0.600000000000 1558314 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": 1084157, "vin": [ { "gen": { "height": 1084147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64f97d5ea89133a95dcfd9b27f0a0e4d646fecbeb3a2167ccf619836fa2a0c91" } } ], "extra": [ 1, 246, 32, 77, 198, 197, 202, 227, 102, 209, 133, 59, 232, 35, 229, 139, 90, 86, 157, 104, 98, 107, 134, 0, 150, 239, 218, 138, 9, 246, 109, 13, 183, 2, 17, 0, 0, 0, 2, 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