Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2ac5717c5f8a7bbe68781a7ee539fdfbecb4c70545b181770e5ffc0e00eb309

Tx prefix hash: 6fcd706c2127e7ab2132431397c61cbc784e0a9993ab3249c5a07d928ea41fb4
Tx public key: a1d34b194e57c0b19dc1c38e763783743db3b65fdc03ddc129a0b7539e577c31
Timestamp: 1581670016 Timestamp [UCT]: 2020-02-14 08:46:56 Age [y:d:h:m:s]: 05:265:02:20:14
Block: 64827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1339919 RingCT/type: yes/0
Extra: 01a1d34b194e57c0b19dc1c38e763783743db3b65fdc03ddc129a0b7539e577c310211000000014ac5aa02000000000000000000

1 output(s) for total of 374.338178361000 dcy

stealth address amount amount idx
00: 54d765ef561c224596aa67aa89df2f6abd3a4b4f4b0ec1ef588f21866c1242c0 374.338178361000 119556 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": 64837, "vin": [ { "gen": { "height": 64827 } } ], "vout": [ { "amount": 374338178361, "target": { "key": "54d765ef561c224596aa67aa89df2f6abd3a4b4f4b0ec1ef588f21866c1242c0" } } ], "extra": [ 1, 161, 211, 75, 25, 78, 87, 192, 177, 157, 193, 195, 142, 118, 55, 131, 116, 61, 179, 182, 95, 220, 3, 221, 193, 41, 160, 183, 83, 158, 87, 124, 49, 2, 17, 0, 0, 0, 1, 74, 197, 170, 2, 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