Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23c1dc13457288c1316fc7e074674b7dfb051b2d0b6e8fbd3682d6656e21729d

Tx prefix hash: cf7559a9822d2d54cecb36f14b41f960c7301ae5877e220a84bc2a8dc2fc2503
Tx public key: ebe1e5a02234d2f78addafdd8f748c555fff54252eaadd00fbdbc63ca7844775
Timestamp: 1722014922 Timestamp [UCT]: 2024-07-26 17:28:42 Age [y:d:h:m:s]: 00:260:03:24:00
Block: 1074253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185840 RingCT/type: yes/0
Extra: 01ebe1e5a02234d2f78addafdd8f748c555fff54252eaadd00fbdbc63ca7844775021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94307b0cf92d32ea042c5fd1e14da2d3debb27e450a7aaaea744d5cc07bfc7b0 0.600000000000 1546766 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": 1074263, "vin": [ { "gen": { "height": 1074253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94307b0cf92d32ea042c5fd1e14da2d3debb27e450a7aaaea744d5cc07bfc7b0" } } ], "extra": [ 1, 235, 225, 229, 160, 34, 52, 210, 247, 138, 221, 175, 221, 143, 116, 140, 85, 95, 255, 84, 37, 46, 170, 221, 0, 251, 219, 198, 60, 167, 132, 71, 117, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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