Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b1d221ddc6aba9211f3a49c9dbab62dda63eb8b44cc6356d9b9b6e08b737301

Tx prefix hash: f61932fc8068596dc7bf9691be7d488fe70d818a6e17cec8cde81d7a5bb75f5e
Tx public key: 0dac6aba08c489c5283217266ac35d9a838ff731edb5c3030e054c60b1e502e5
Timestamp: 1727464353 Timestamp [UCT]: 2024-09-27 19:12:33 Age [y:d:h:m:s]: 00:117:08:40:58
Block: 1119437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83876 RingCT/type: yes/0
Extra: 010dac6aba08c489c5283217266ac35d9a838ff731edb5c3030e054c60b1e502e502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4e6037c75aafe24d550be8f514946872438e40fa5b619d42f4b699b49bb47a5 0.600000000000 1600996 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": 1119447, "vin": [ { "gen": { "height": 1119437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4e6037c75aafe24d550be8f514946872438e40fa5b619d42f4b699b49bb47a5" } } ], "extra": [ 1, 13, 172, 106, 186, 8, 196, 137, 197, 40, 50, 23, 38, 106, 195, 93, 154, 131, 143, 247, 49, 237, 181, 195, 3, 14, 5, 76, 96, 177, 229, 2, 229, 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