Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 395ca2d439fdac622925d824231f8d2c7bcc1e049a96d12f132062306f4209e7

Tx prefix hash: bab416fd0a360b16a5d8822e7728ab0f60770c0a77bc3efde7ad1d0f9deae540
Tx public key: dd6b64109846371886484478d3a1b17f8c4e4850b535435bb687b6c7eef2dbc8
Timestamp: 1736742658 Timestamp [UCT]: 2025-01-13 04:30:58 Age [y:d:h:m:s]: 00:075:06:43:01
Block: 1196221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53577 RingCT/type: yes/0
Extra: 01dd6b64109846371886484478d3a1b17f8c4e4850b535435bb687b6c7eef2dbc8021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b202a80198696af4c1fc69199c6556ce6b4f2649c25bdef7639bcdaafc21d6dd 0.600000000000 1682818 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": 1196231, "vin": [ { "gen": { "height": 1196221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b202a80198696af4c1fc69199c6556ce6b4f2649c25bdef7639bcdaafc21d6dd" } } ], "extra": [ 1, 221, 107, 100, 16, 152, 70, 55, 24, 134, 72, 68, 120, 211, 161, 177, 127, 140, 78, 72, 80, 181, 53, 67, 91, 182, 135, 182, 199, 238, 242, 219, 200, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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