Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7d57f3e97c0e26860d3c2f1031a4d41c5457310d34d2c57807b94a5825e299d

Tx prefix hash: 04df480cf48c16b4bbde9ac0e3f824fe8ea402398ecce7cc27eb83ae75228404
Tx public key: ba61446cb4bc802b30484c298e4a2fc9fcb56786b1273044296621e94c3edef6
Timestamp: 1723202215 Timestamp [UCT]: 2024-08-09 11:16:55 Age [y:d:h:m:s]: 00:074:12:03:04
Block: 1084105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53335 RingCT/type: yes/0
Extra: 01ba61446cb4bc802b30484c298e4a2fc9fcb56786b1273044296621e94c3edef602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9418e9df3b9c705a451d687737aafe5aea6bc1f8c9f188df8d0b6cdeb4961525 0.600000000000 1558260 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": 1084115, "vin": [ { "gen": { "height": 1084105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9418e9df3b9c705a451d687737aafe5aea6bc1f8c9f188df8d0b6cdeb4961525" } } ], "extra": [ 1, 186, 97, 68, 108, 180, 188, 128, 43, 48, 72, 76, 41, 142, 74, 47, 201, 252, 181, 103, 134, 177, 39, 48, 68, 41, 102, 33, 233, 76, 62, 222, 246, 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