Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee1bbd33b6b37b83c3a8b720829c2b04ab328106a0af57f2b598fc7627c4088d

Tx prefix hash: 3f33cb1514b6ce7ce5199986c3cfe0cc80502bb7216bb14af679d428d1e6da0e
Tx public key: ab0e7fce631c68b3d4ccc7bc7cbf13afb9131ebaf0f43729eefac7aa29650f3d
Timestamp: 1578823458 Timestamp [UCT]: 2020-01-12 10:04:18 Age [y:d:h:m:s]: 04:352:01:15:59
Block: 43853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1141122 RingCT/type: yes/0
Extra: 01ab0e7fce631c68b3d4ccc7bc7cbf13afb9131ebaf0f43729eefac7aa29650f3d02110000012aff58ae94000000000000000000

1 output(s) for total of 439.235717674000 dcy

stealth address amount amount idx
00: 6427b32a7b2210cc1f3d7638acc31fa2908355bffb9ec26af4ebe04203997476 439.235717674000 79571 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": 43863, "vin": [ { "gen": { "height": 43853 } } ], "vout": [ { "amount": 439235717674, "target": { "key": "6427b32a7b2210cc1f3d7638acc31fa2908355bffb9ec26af4ebe04203997476" } } ], "extra": [ 1, 171, 14, 127, 206, 99, 28, 104, 179, 212, 204, 199, 188, 124, 191, 19, 175, 185, 19, 30, 186, 240, 244, 55, 41, 238, 250, 199, 170, 41, 101, 15, 61, 2, 17, 0, 0, 1, 42, 255, 88, 174, 148, 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