Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb48bec93c349d6116b97cac03e5fdc6c717acb650ba74c16f320191b30e21b2

Tx prefix hash: 11e38d174545140c156a2b125b3b1bef51e140f99aa08e0467a1108aff101719
Tx public key: 6a3697dc0ca3aaacf4539f7cb167bd577dd737fd601f8b5feaa7f9fbea77a8c4
Timestamp: 1752842412 Timestamp [UCT]: 2025-07-18 12:40:12 Age [y:d:h:m:s]: 00:118:09:01:11
Block: 1328119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83385 RingCT/type: yes/0
Extra: 016a3697dc0ca3aaacf4539f7cb167bd577dd737fd601f8b5feaa7f9fbea77a8c4021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1b1021e164ef0c27ffaa312fd292d8fa2c235c22a04fff94e28b28b4bafa617 0.600000000000 1815880 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": 1328129, "vin": [ { "gen": { "height": 1328119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1b1021e164ef0c27ffaa312fd292d8fa2c235c22a04fff94e28b28b4bafa617" } } ], "extra": [ 1, 106, 54, 151, 220, 12, 163, 170, 172, 244, 83, 159, 124, 177, 103, 189, 87, 125, 215, 55, 253, 96, 31, 139, 95, 234, 167, 249, 251, 234, 119, 168, 196, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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