Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ea0cdc938a38f75545cdf789d3f2baed1ae820b9e55beb9a417528d93f33261

Tx prefix hash: 3111d5734aeeeba192987a8cacf9cdbc1e95eaa838a11833e5803166ca66b591
Tx public key: 86763ae9ba5d50d13eb1833de0693ec86cda7fdbb77e8c063d27508c9d07b408
Timestamp: 1752896828 Timestamp [UCT]: 2025-07-19 03:47:08 Age [y:d:h:m:s]: 00:168:22:54:07
Block: 1328567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119609 RingCT/type: yes/0
Extra: 0186763ae9ba5d50d13eb1833de0693ec86cda7fdbb77e8c063d27508c9d07b4080211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e87b6b5965bba7cac40f862d6f95d54cfcf77bdd68cd2e3df001ece9f47e86d7 0.600000000000 1816330 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": 1328577, "vin": [ { "gen": { "height": 1328567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e87b6b5965bba7cac40f862d6f95d54cfcf77bdd68cd2e3df001ece9f47e86d7" } } ], "extra": [ 1, 134, 118, 58, 233, 186, 93, 80, 209, 62, 177, 131, 61, 224, 105, 62, 200, 108, 218, 127, 219, 183, 126, 140, 6, 61, 39, 80, 140, 157, 7, 180, 8, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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