Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2b0ca9d3d62066ae7fb6aec8f1146345dc7cec9ace827e443ee7344de0e5e0b

Tx prefix hash: 342c83c2d17bf45b4b00177d5e0bff6c97c9d0d39ecc12c8ce16131692247b74
Tx public key: 423f133b2c35df0ca2092fbdc8f3bbf91caa6ae145450effcb8fb900f5410c8b
Timestamp: 1744087265 Timestamp [UCT]: 2025-04-08 04:41:05 Age [y:d:h:m:s]: 00:028:17:39:33
Block: 1256734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20573 RingCT/type: yes/0
Extra: 01423f133b2c35df0ca2092fbdc8f3bbf91caa6ae145450effcb8fb900f5410c8b021100000008dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c2288ca5cd2f5d80dc366675bb7e1cc1bcefd9afc48ab84b7a48cf59c601ca4 0.600000000000 1743851 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": 1256744, "vin": [ { "gen": { "height": 1256734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c2288ca5cd2f5d80dc366675bb7e1cc1bcefd9afc48ab84b7a48cf59c601ca4" } } ], "extra": [ 1, 66, 63, 19, 59, 44, 53, 223, 12, 162, 9, 47, 189, 200, 243, 187, 249, 28, 170, 106, 225, 69, 69, 14, 255, 203, 143, 185, 0, 245, 65, 12, 139, 2, 17, 0, 0, 0, 8, 223, 195, 186, 73, 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