Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 228b9ab9be0d848486b19fc9e4252225218b5ccc28728e5576f7a633fc112d7c

Tx prefix hash: f5c17a494d0d17adf8500af085db3d497362d1318f195a9f91d4b9dc55c30c52
Tx public key: 7969b5d7626bc93d8fbc64d6eb73b66f2a0f48bc183d92e973df252f4abbbbcd
Timestamp: 1745281083 Timestamp [UCT]: 2025-04-22 00:18:03 Age [y:d:h:m:s]: 00:261:17:02:43
Block: 1266628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184847 RingCT/type: yes/0
Extra: 017969b5d7626bc93d8fbc64d6eb73b66f2a0f48bc183d92e973df252f4abbbbcd0211000000026c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b06c0eac1ad5c957dbd28a10619bf852c6a44da1cf45cfed94f637e3ac79cf18 0.600000000000 1753849 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": 1266638, "vin": [ { "gen": { "height": 1266628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b06c0eac1ad5c957dbd28a10619bf852c6a44da1cf45cfed94f637e3ac79cf18" } } ], "extra": [ 1, 121, 105, 181, 215, 98, 107, 201, 61, 143, 188, 100, 214, 235, 115, 182, 111, 42, 15, 72, 188, 24, 61, 146, 233, 115, 223, 37, 47, 74, 187, 187, 205, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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