Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1663b69692ab4a27c91017735662e38a58891a4c07c42df3423472f45b410ba8

Tx prefix hash: 691b0e6ea10374b94bf9e856ad7d9398b4fc45d294504c2277ede4a99142769c
Tx public key: 7ac5ccadab0643cad654dfd4d34d4d5d264c454193f300d9e295766874d93143
Timestamp: 1577575760 Timestamp [UCT]: 2019-12-28 23:29:20 Age [y:d:h:m:s]: 04:333:21:21:25
Block: 33908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127741 RingCT/type: yes/0
Extra: 017ac5ccadab0643cad654dfd4d34d4d5d264c454193f300d9e295766874d9314302110000002be39b962a000000000000000000

1 output(s) for total of 473.859483454000 dcy

stealth address amount amount idx
00: d93f965f0f62ff8e9597dd8dc26a1c098df2d73ed717c991ddb83daefe453fba 473.859483454000 56956 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": 33918, "vin": [ { "gen": { "height": 33908 } } ], "vout": [ { "amount": 473859483454, "target": { "key": "d93f965f0f62ff8e9597dd8dc26a1c098df2d73ed717c991ddb83daefe453fba" } } ], "extra": [ 1, 122, 197, 204, 173, 171, 6, 67, 202, 214, 84, 223, 212, 211, 77, 77, 93, 38, 76, 69, 65, 147, 243, 0, 217, 226, 149, 118, 104, 116, 217, 49, 67, 2, 17, 0, 0, 0, 43, 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