Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c14fac84d10efd7d05de2ce85cfac8bab6e97be07807b7eede3ff34962427a34

Tx prefix hash: 49ef100abec43b566ddd4c34fa9f15034dee0f1fa5bf18385ec9b84049053c5a
Tx public key: 3ec5467abbfdeeacddc7eb5d3e5c5094d7c99b4c0b07fab295b431ba471a4f0c
Timestamp: 1762985830 Timestamp [UCT]: 2025-11-12 22:17:10 Age [y:d:h:m:s]: 00:051:11:27:38
Block: 1410801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36872 RingCT/type: yes/0
Extra: 013ec5467abbfdeeacddc7eb5d3e5c5094d7c99b4c0b07fab295b431ba471a4f0c021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c608c83a97551d50b71576e004283cd6dfcbe818917c6eaf53654cef79ee00ea 0.600000000000 1899256 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": 1410811, "vin": [ { "gen": { "height": 1410801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c608c83a97551d50b71576e004283cd6dfcbe818917c6eaf53654cef79ee00ea" } } ], "extra": [ 1, 62, 197, 70, 122, 187, 253, 238, 172, 221, 199, 235, 93, 62, 92, 80, 148, 215, 201, 155, 76, 11, 7, 250, 178, 149, 180, 49, 186, 71, 26, 79, 12, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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