Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c03ddfe0b3cee252ed59765fe96f3e9020306f7b040862ac28f2d1dd54dc8c2

Tx prefix hash: d1dcfb11ffc7d370d48279a07cf45e16ad7784dcd2f28c2f76a72f88c5704f15
Tx public key: dc3cb25fa0ce1a970677e882b8a64faee47312491c3aafa1598155e48fcb9a14
Timestamp: 1738665126 Timestamp [UCT]: 2025-02-04 10:32:06 Age [y:d:h:m:s]: 00:290:04:58:12
Block: 1211865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205168 RingCT/type: yes/0
Extra: 01dc3cb25fa0ce1a970677e882b8a64faee47312491c3aafa1598155e48fcb9a14021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bca3e5ef22aa3c4c6c6e3a590ff5f8d76814dd879d3c64edd2564dcac6e8fc6c 0.600000000000 1698632 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": 1211875, "vin": [ { "gen": { "height": 1211865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bca3e5ef22aa3c4c6c6e3a590ff5f8d76814dd879d3c64edd2564dcac6e8fc6c" } } ], "extra": [ 1, 220, 60, 178, 95, 160, 206, 26, 151, 6, 119, 232, 130, 184, 166, 79, 174, 228, 115, 18, 73, 28, 58, 175, 161, 89, 129, 85, 228, 143, 203, 154, 20, 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