Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fc6ea7136ba24ab56b3d0b1f14f2fa4f18bb6f520735434ac5080cda825521d

Tx prefix hash: 658e0232ef5cac3d9da04d8ee6fa96023851583fadebb570bd68776d63013343
Tx public key: 4f48cc7eadaefa91a3d02cd18fec0b87394a06f2de20c710b7f1e09396487d8b
Timestamp: 1716629535 Timestamp [UCT]: 2024-05-25 09:32:15 Age [y:d:h:m:s]: 00:315:17:27:05
Block: 1029622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225642 RingCT/type: yes/0
Extra: 014f48cc7eadaefa91a3d02cd18fec0b87394a06f2de20c710b7f1e09396487d8b02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ea7c3911e6d0bcc9e26185e72b6d02579c2b9036ac9af73e056b7d85de0f353 0.600000000000 1497761 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": 1029632, "vin": [ { "gen": { "height": 1029622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ea7c3911e6d0bcc9e26185e72b6d02579c2b9036ac9af73e056b7d85de0f353" } } ], "extra": [ 1, 79, 72, 204, 126, 173, 174, 250, 145, 163, 208, 44, 209, 143, 236, 11, 135, 57, 74, 6, 242, 222, 32, 199, 16, 183, 241, 224, 147, 150, 72, 125, 139, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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