Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 527f68feaab02206b59c9026cc509770ffdf4b27a907322883543aec6a4b7013

Tx prefix hash: 2bba21818905733a2e613670be84f0af8b2029b6e93018b25756429255040ff2
Tx public key: c4c7f597f843f8f1b682b7475b81bae0dcd9885a78466e8cf3d0aa5c3d80ab2c
Timestamp: 1751343418 Timestamp [UCT]: 2025-07-01 04:16:58 Age [y:d:h:m:s]: 00:136:19:48:44
Block: 1316308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95981 RingCT/type: yes/0
Extra: 01c4c7f597f843f8f1b682b7475b81bae0dcd9885a78466e8cf3d0aa5c3d80ab2c02110000000abf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3781eb5812ef3d6d855671c7c34012d590d2e597ca184f6f57cf80f9645dbeab 0.600000000000 1803967 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": 1316318, "vin": [ { "gen": { "height": 1316308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3781eb5812ef3d6d855671c7c34012d590d2e597ca184f6f57cf80f9645dbeab" } } ], "extra": [ 1, 196, 199, 245, 151, 248, 67, 248, 241, 182, 130, 183, 71, 91, 129, 186, 224, 220, 217, 136, 90, 120, 70, 110, 140, 243, 208, 170, 92, 61, 128, 171, 44, 2, 17, 0, 0, 0, 10, 191, 81, 178, 162, 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