Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c00e1b565103a82a00f68ac9e442fc8075189f9cbea697e84fb8738f5765e5d

Tx prefix hash: 0149404455f616062410faeb5839d3f90a610ee8069b672c7c35ed8106e8a156
Tx public key: 64f6bbb7fd63f2f8e49202710d0d5492b570ef7b405280efafe9533ecb6e248c
Timestamp: 1750752765 Timestamp [UCT]: 2025-06-24 08:12:45 Age [y:d:h:m:s]: 00:149:10:13:04
Block: 1311689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104716 RingCT/type: yes/0
Extra: 0164f6bbb7fd63f2f8e49202710d0d5492b570ef7b405280efafe9533ecb6e248c021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0001744d385f0812abeb7707207db6c0e74832aee92706fbf306a3ae3cde872c 0.600000000000 1799318 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": 1311699, "vin": [ { "gen": { "height": 1311689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0001744d385f0812abeb7707207db6c0e74832aee92706fbf306a3ae3cde872c" } } ], "extra": [ 1, 100, 246, 187, 183, 253, 99, 242, 248, 228, 146, 2, 113, 13, 13, 84, 146, 181, 112, 239, 123, 64, 82, 128, 239, 175, 233, 83, 62, 203, 110, 36, 140, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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