Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91e1bf46aea8adc083d4e0bf8081f6bf0800fd62ef133c1a78a7a22bcbf30abf

Tx prefix hash: ffaff551a835fc38315f5287c601db1097131a42c6d686377914533945c183c8
Tx public key: c86c9d19fc4ac4e364a2e4aa0f375fecbf28d91ae2de7e1208f50b3c29373a21
Timestamp: 1760767968 Timestamp [UCT]: 2025-10-18 06:12:48 Age [y:d:h:m:s]: 00:082:17:44:23
Block: 1392436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59237 RingCT/type: yes/0
Extra: 01c86c9d19fc4ac4e364a2e4aa0f375fecbf28d91ae2de7e1208f50b3c29373a21021100000002df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f0993f2815a00b3062c7627236428b3fe5f58d47fc0cdd5e701f794368344c4 0.600000000000 1880687 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": 1392446, "vin": [ { "gen": { "height": 1392436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f0993f2815a00b3062c7627236428b3fe5f58d47fc0cdd5e701f794368344c4" } } ], "extra": [ 1, 200, 108, 157, 25, 252, 74, 196, 227, 100, 162, 228, 170, 15, 55, 95, 236, 191, 40, 217, 26, 226, 222, 126, 18, 8, 245, 11, 60, 41, 55, 58, 33, 2, 17, 0, 0, 0, 2, 223, 90, 36, 122, 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