Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0124f4ab3428b0aa138cd7a3f7aec0aefda3410c28f2ca0f18b593174af2689d

Tx prefix hash: b1e754604b4622a21b0d7dfcf6d638d137110d6e9bab3b2cf140fb02a41c1955
Tx public key: 822a7a1146a270a1d5e5c19dff7e7535f4c7c49d477f00efb0771a0d5e858a8a
Timestamp: 1750212850 Timestamp [UCT]: 2025-06-18 02:14:10 Age [y:d:h:m:s]: 00:145:21:08:28
Block: 1307354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102049 RingCT/type: yes/0
Extra: 01822a7a1146a270a1d5e5c19dff7e7535f4c7c49d477f00efb0771a0d5e858a8a021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b6d6ad452d46f68baec8b4aeff39c8af4b65b18cc134fc28c0ec7fddaead513 0.600000000000 1794965 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": 1307364, "vin": [ { "gen": { "height": 1307354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b6d6ad452d46f68baec8b4aeff39c8af4b65b18cc134fc28c0ec7fddaead513" } } ], "extra": [ 1, 130, 42, 122, 17, 70, 162, 112, 161, 213, 229, 193, 157, 255, 126, 117, 53, 244, 199, 196, 157, 71, 127, 0, 239, 176, 119, 26, 13, 94, 133, 138, 138, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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