Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 966a229997390cb91e25f61511b0bc7f89497b0c4c0390a48f935a643a419a00

Tx prefix hash: e76da7e570c274dd5716dca4a8d2b075e3443820210ba040cc90fe3da64ab8bf
Tx public key: c0c30b622c37f9f02f1206d2826783d331b9b807c23be73ca497d0fd70af5fd8
Timestamp: 1621598731 Timestamp [UCT]: 2021-05-21 12:05:31 Age [y:d:h:m:s]: 03:290:04:00:09
Block: 264544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 968949 RingCT/type: yes/0
Extra: 01c0c30b622c37f9f02f1206d2826783d331b9b807c23be73ca497d0fd70af5fd80211000000140bb79a4a000000000000000000

1 output(s) for total of 81.556100487000 dcy

stealth address amount amount idx
00: d0e5fe4b1db8a0d16f34584bacacbad4a5d16e83ea9d63d40649d47500df921d 81.556100487000 556258 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": 264554, "vin": [ { "gen": { "height": 264544 } } ], "vout": [ { "amount": 81556100487, "target": { "key": "d0e5fe4b1db8a0d16f34584bacacbad4a5d16e83ea9d63d40649d47500df921d" } } ], "extra": [ 1, 192, 195, 11, 98, 44, 55, 249, 240, 47, 18, 6, 210, 130, 103, 131, 211, 49, 185, 184, 7, 194, 59, 231, 60, 164, 151, 208, 253, 112, 175, 95, 216, 2, 17, 0, 0, 0, 20, 11, 183, 154, 74, 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