Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cf4efc0bd5f725ca078deaea8f0b1579a46cb06e596d9de414a78ca1e6ed1c2

Tx prefix hash: 410fe3d7e1b5d40e201905229f8346ca6822eeece2b15a531ed2bae7988b04e9
Tx public key: 068a0c788ee961a5427618682c3b025a2d2b2629c038820316a01b8f5c565301
Timestamp: 1760525598 Timestamp [UCT]: 2025-10-15 10:53:18 Age [y:d:h:m:s]: 00:069:05:04:22
Block: 1390422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49538 RingCT/type: yes/0
Extra: 01068a0c788ee961a5427618682c3b025a2d2b2629c038820316a01b8f5c5653010211000000047b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a57512cd76acb7a0e2b3e6ae1beff18019dcef6716fa45d194de32bb55c1966 0.600000000000 1878665 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": 1390432, "vin": [ { "gen": { "height": 1390422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a57512cd76acb7a0e2b3e6ae1beff18019dcef6716fa45d194de32bb55c1966" } } ], "extra": [ 1, 6, 138, 12, 120, 142, 233, 97, 165, 66, 118, 24, 104, 44, 59, 2, 90, 45, 43, 38, 41, 192, 56, 130, 3, 22, 160, 27, 143, 92, 86, 83, 1, 2, 17, 0, 0, 0, 4, 123, 30, 81, 172, 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