Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a68dd4cdc4ef179866b6d0405d7ecb5c9519a4fa1f4c98a811436b3d609e572e

Tx prefix hash: e18b4d7750c369dd93e106add15a4d46e4cdfd430c12f3649731499645866603
Tx public key: 92fb6006e4c64944ff272812fc81085016b0706db8bbd8c9a6b4024985ee8329
Timestamp: 1674636784 Timestamp [UCT]: 2023-01-25 08:53:04 Age [y:d:h:m:s]: 01:353:04:00:22
Block: 682351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513399 RingCT/type: yes/0
Extra: 0192fb6006e4c64944ff272812fc81085016b0706db8bbd8c9a6b4024985ee83290211000000015029cbac000000000000000000

1 output(s) for total of 3.365796223000 dcy

stealth address amount amount idx
00: 05302f6d2ffae1dc027e13d61d885285f2d17c1ea64c9e0c7898b7b6200d3f7f 3.365796223000 1124470 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": 682361, "vin": [ { "gen": { "height": 682351 } } ], "vout": [ { "amount": 3365796223, "target": { "key": "05302f6d2ffae1dc027e13d61d885285f2d17c1ea64c9e0c7898b7b6200d3f7f" } } ], "extra": [ 1, 146, 251, 96, 6, 228, 198, 73, 68, 255, 39, 40, 18, 252, 129, 8, 80, 22, 176, 112, 109, 184, 187, 216, 201, 166, 180, 2, 73, 133, 238, 131, 41, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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