Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b4dfa3c48d80bb29699ccf64ced8f0a94d9ae166d5434f81390e675ae2fc8c8

Tx prefix hash: 777941e1f88c1ca6437e4d10dfb4524bf5f16eebf8c211946ad0d5f5d2b8d734
Tx public key: af62612ed4b23415d9f04cc599232db312b92e8bbe9c7be95a7109892ca90414
Timestamp: 1762360192 Timestamp [UCT]: 2025-11-05 16:29:52 Age [y:d:h:m:s]: 00:066:00:30:32
Block: 1405606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47298 RingCT/type: yes/0
Extra: 01af62612ed4b23415d9f04cc599232db312b92e8bbe9c7be95a7109892ca904140211000000035dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e338847c11988bcbbb3aec8c9ef490039fc24dc634d0c05a386fb32c296c8510 0.600000000000 1893987 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": 1405616, "vin": [ { "gen": { "height": 1405606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e338847c11988bcbbb3aec8c9ef490039fc24dc634d0c05a386fb32c296c8510" } } ], "extra": [ 1, 175, 98, 97, 46, 212, 178, 52, 21, 217, 240, 76, 197, 153, 35, 45, 179, 18, 185, 46, 139, 190, 156, 123, 233, 90, 113, 9, 137, 44, 169, 4, 20, 2, 17, 0, 0, 0, 3, 93, 251, 190, 42, 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