Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 499d255063a6af1ce534ee7e25c84a76babe4e2456b6b1bf447a3e366ca9a2a5

Tx prefix hash: 363190333150da553bf4551fe74b125bb36a16aff6a807d6f3fb2c554728868b
Tx public key: 83297fa8c71e3e3cb34dae54baf0d58454d180b6281c0fa1cc6bfce440bc6c9d
Timestamp: 1711329668 Timestamp [UCT]: 2024-03-25 01:21:08 Age [y:d:h:m:s]: 01:029:15:38:50
Block: 985700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282145 RingCT/type: yes/0
Extra: 0183297fa8c71e3e3cb34dae54baf0d58454d180b6281c0fa1cc6bfce440bc6c9d02110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb1f219495ae6c8d0e0c7d5834423d61d48339116bbc950dd6a074c736114ec4 0.600000000000 1445917 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": 985710, "vin": [ { "gen": { "height": 985700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb1f219495ae6c8d0e0c7d5834423d61d48339116bbc950dd6a074c736114ec4" } } ], "extra": [ 1, 131, 41, 127, 168, 199, 30, 62, 60, 179, 77, 174, 84, 186, 240, 213, 132, 84, 209, 128, 182, 40, 28, 15, 161, 204, 107, 252, 228, 64, 188, 108, 157, 2, 17, 0, 0, 0, 9, 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