Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9963eea092e2980d2501017fea48512ff2af4dc0d8334a454de95ba1c493914

Tx prefix hash: 6c6b481d4dfd81d79592063bb4cbeb713afe4aa0b5d32d66768512f32acb2fb2
Tx public key: 3286d0d1c7d8c00cb63030033133cff319f52af9b42e0badb6635382aed93de2
Timestamp: 1721035534 Timestamp [UCT]: 2024-07-15 09:25:34 Age [y:d:h:m:s]: 00:180:07:40:40
Block: 1066148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129012 RingCT/type: yes/0
Extra: 013286d0d1c7d8c00cb63030033133cff319f52af9b42e0badb6635382aed93de202110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b65e0171076abdd31203c901178013b3f9ce080f421a09b244b6d1376e78799 0.600000000000 1536721 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": 1066158, "vin": [ { "gen": { "height": 1066148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b65e0171076abdd31203c901178013b3f9ce080f421a09b244b6d1376e78799" } } ], "extra": [ 1, 50, 134, 208, 209, 199, 216, 192, 12, 182, 48, 48, 3, 49, 51, 207, 243, 25, 245, 42, 249, 180, 46, 11, 173, 182, 99, 83, 130, 174, 217, 61, 226, 2, 17, 0, 0, 0, 1, 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