Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec0edea00ef4ce883a45615832412a0576a38a38c5e887b579de47007243c054

Tx prefix hash: 6bcf2550b51cb29f5fa43555c1dd12c4b203e5287d0ced78d29e262aea479ebc
Tx public key: 2087e26f70a46a0c359891fda4af6dc2640a0ee1200e24e60ba1a8091063c11e
Timestamp: 1577396089 Timestamp [UCT]: 2019-12-26 21:34:49 Age [y:d:h:m:s]: 05:045:03:09:59
Block: 32462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181978 RingCT/type: yes/0
Extra: 012087e26f70a46a0c359891fda4af6dc2640a0ee1200e24e60ba1a8091063c11e021100000095e39b962a000000000000000000

1 output(s) for total of 479.116113374000 dcy

stealth address amount amount idx
00: fd11759a60edd077acbef4e07b617c9693ce1769c0cc620edf8ec03fe969a8a2 479.116113374000 53990 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": 32472, "vin": [ { "gen": { "height": 32462 } } ], "vout": [ { "amount": 479116113374, "target": { "key": "fd11759a60edd077acbef4e07b617c9693ce1769c0cc620edf8ec03fe969a8a2" } } ], "extra": [ 1, 32, 135, 226, 111, 112, 164, 106, 12, 53, 152, 145, 253, 164, 175, 109, 194, 100, 10, 14, 225, 32, 14, 36, 230, 11, 161, 168, 9, 16, 99, 193, 30, 2, 17, 0, 0, 0, 149, 227, 155, 150, 42, 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