Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0f107109473efbae6ce2d6b3a9cb0724e1f914a87c4037b24d4f575bef7cc52

Tx prefix hash: 3d32a2f949d45507d5dfcab6778702d660eeb37ec582ca1c342a3e2808217d03
Tx public key: 4c9bde36b453e1b88907591e5bc59c5300deb666a25e02013b314e07d009f503
Timestamp: 1670416512 Timestamp [UCT]: 2022-12-07 12:35:12 Age [y:d:h:m:s]: 02:043:00:17:28
Block: 647371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 552693 RingCT/type: yes/0
Extra: 014c9bde36b453e1b88907591e5bc59c5300deb666a25e02013b314e07d009f5030211000000027e406890000000000000000000

1 output(s) for total of 4.395326393000 dcy

stealth address amount amount idx
00: ae9b7f7d65cbf7afe4fc8af0bf1d849688b05b5cb8d757e394034f23bb4f8656 4.395326393000 1087642 of 0

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": 647381, "vin": [ { "gen": { "height": 647371 } } ], "vout": [ { "amount": 4395326393, "target": { "key": "ae9b7f7d65cbf7afe4fc8af0bf1d849688b05b5cb8d757e394034f23bb4f8656" } } ], "extra": [ 1, 76, 155, 222, 54, 180, 83, 225, 184, 137, 7, 89, 30, 91, 197, 156, 83, 0, 222, 182, 102, 162, 94, 2, 1, 59, 49, 78, 7, 208, 9, 245, 3, 2, 17, 0, 0, 0, 2, 126, 64, 104, 144, 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