Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1bf4ecd035a5cd4a37e374c14c46342483c290a1bb3225ce3e175684d5efab6

Tx prefix hash: 9eaf8618bcebba8f5b8b9e542c7a929014144cf01730d87141fbcc33112ff3f4
Tx public key: 82fa5c51d8144c05e8b8e9384d4b5e0d2c264c1e41d7d1644e9a8df77200fd0a
Timestamp: 1761839180 Timestamp [UCT]: 2025-10-30 15:46:20 Age [y:d:h:m:s]: 00:022:08:41:47
Block: 1401305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16002 RingCT/type: yes/0
Extra: 0182fa5c51d8144c05e8b8e9384d4b5e0d2c264c1e41d7d1644e9a8df77200fd0a02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e219f160201e0f70adae6aef95a1a40c5c4508499d01cb1c7db56b2fb6cb4d17 0.600000000000 1889624 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": 1401315, "vin": [ { "gen": { "height": 1401305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e219f160201e0f70adae6aef95a1a40c5c4508499d01cb1c7db56b2fb6cb4d17" } } ], "extra": [ 1, 130, 250, 92, 81, 216, 20, 76, 5, 232, 184, 233, 56, 77, 75, 94, 13, 44, 38, 76, 30, 65, 215, 209, 100, 78, 154, 141, 247, 114, 0, 253, 10, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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