Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1afcc9a40d79201b46a03161cf1bfb85aaf07feb463220f65f5368db116f5e4e

Tx prefix hash: f1b0a09b7064415e9a64181f0e3a44becaaa44da82f70fd105a3c9cf78b1b424
Tx public key: 9a3075a25f91377f04c56e7c8cc6c72f158d4a5ce107ecabe4899aee294a1a6d
Timestamp: 1733400586 Timestamp [UCT]: 2024-12-05 12:09:46 Age [y:d:h:m:s]: 00:189:00:29:05
Block: 1168554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134891 RingCT/type: yes/0
Extra: 019a3075a25f91377f04c56e7c8cc6c72f158d4a5ce107ecabe4899aee294a1a6d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ad255d1cd40da806bc7c96155aae67522e0cf888ff84eccda4f856f5f25ed41 0.600000000000 1654263 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": 1168564, "vin": [ { "gen": { "height": 1168554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ad255d1cd40da806bc7c96155aae67522e0cf888ff84eccda4f856f5f25ed41" } } ], "extra": [ 1, 154, 48, 117, 162, 95, 145, 55, 127, 4, 197, 110, 124, 140, 198, 199, 47, 21, 141, 74, 92, 225, 7, 236, 171, 228, 137, 154, 238, 41, 74, 26, 109, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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