Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5373e17e1752d519de320a5d1ba83eb9a70be44bff6c74d805b43f5174ab30b5

Tx prefix hash: a21929ad1b4f634d701cc0bae5b71bc38a6d14958f8afcff8c089017883d0791
Tx public key: 73e311b6331274bf3d12e89ab5fea0d528fa344b956f87a4d878affc9a2297f7
Timestamp: 1704260579 Timestamp [UCT]: 2024-01-03 05:42:59 Age [y:d:h:m:s]: 00:360:05:45:05
Block: 927055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257924 RingCT/type: yes/0
Extra: 0173e311b6331274bf3d12e89ab5fea0d528fa344b956f87a4d878affc9a2297f70211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70e51034c46d3fe1e7b6ff4d4d62615999bfca7313f3aad01792d56b45824043 0.600000000000 1384855 of 15

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": 927065, "vin": [ { "gen": { "height": 927055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70e51034c46d3fe1e7b6ff4d4d62615999bfca7313f3aad01792d56b45824043" } } ], "extra": [ 1, 115, 227, 17, 182, 51, 18, 116, 191, 61, 18, 232, 154, 181, 254, 160, 213, 40, 250, 52, 75, 149, 111, 135, 164, 216, 120, 175, 252, 154, 34, 151, 247, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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