Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee5fe04c3d82ed13ac60083a573c1de9b212398a01b9252262ccfe1b7f506023

Tx prefix hash: fc02a9f344ceb9245da5652ccbdc8d663b0bed8fdb56a97d8f051a07d0203b4c
Tx public key: f329af98232572a6c889e1fb786851d3dffd984fd2e25a8619aa39bd592c9be6
Timestamp: 1578178680 Timestamp [UCT]: 2020-01-04 22:58:00 Age [y:d:h:m:s]: 05:147:06:10:29
Block: 38843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1255129 RingCT/type: yes/0
Extra: 01f329af98232572a6c889e1fb786851d3dffd984fd2e25a8619aa39bd592c9be6021100000020dcee4b4d000000000000000000

1 output(s) for total of 456.349801366000 dcy

stealth address amount amount idx
00: 9d859e69ed318c35d9ab7eb2a00c079954e6624c9d7ba2f3f141606da8bd920f 456.349801366000 66526 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": 38853, "vin": [ { "gen": { "height": 38843 } } ], "vout": [ { "amount": 456349801366, "target": { "key": "9d859e69ed318c35d9ab7eb2a00c079954e6624c9d7ba2f3f141606da8bd920f" } } ], "extra": [ 1, 243, 41, 175, 152, 35, 37, 114, 166, 200, 137, 225, 251, 120, 104, 81, 211, 223, 253, 152, 79, 210, 226, 90, 134, 25, 170, 57, 189, 89, 44, 155, 230, 2, 17, 0, 0, 0, 32, 220, 238, 75, 77, 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