Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3de15b1b2d7f75bfb138e37fb0cf06fe7ea63a9f039357affbf7166138d5db5b

Tx prefix hash: ef2888c4bb753406f5ba835f5d93138742d26b925ee944a43be022698ea21602
Tx public key: 6f2d61a2a0ac5f89b3484d940b1a52f34311129e0d57d9215cdfe1ea0fdc9ef6
Timestamp: 1728742213 Timestamp [UCT]: 2024-10-12 14:10:13 Age [y:d:h:m:s]: 00:251:19:41:12
Block: 1130034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179642 RingCT/type: yes/0
Extra: 016f2d61a2a0ac5f89b3484d940b1a52f34311129e0d57d9215cdfe1ea0fdc9ef602110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f1e68363a98340e0c69a7d97105e757c93a1d34fbdfa571f2fd72d9af98364c 0.600000000000 1612905 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": 1130044, "vin": [ { "gen": { "height": 1130034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f1e68363a98340e0c69a7d97105e757c93a1d34fbdfa571f2fd72d9af98364c" } } ], "extra": [ 1, 111, 45, 97, 162, 160, 172, 95, 137, 179, 72, 77, 148, 11, 26, 82, 243, 67, 17, 18, 158, 13, 87, 217, 33, 92, 223, 225, 234, 15, 220, 158, 246, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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