Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 199be737f3d6c0d81afca6c10033b6bd1fda13aff398eec09f951440af0f6235

Tx prefix hash: 0a28da9327d96b2a685b67522848819e0a0e8b2c913cbf5a200aaf9df312d0fd
Tx public key: 6683f728285d4f56ec555e88ada4f3e533d9f975a081406f44813d08b83b2bc9
Timestamp: 1741810377 Timestamp [UCT]: 2025-03-12 20:12:57 Age [y:d:h:m:s]: 00:300:16:00:01
Block: 1237916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212691 RingCT/type: yes/0
Extra: 016683f728285d4f56ec555e88ada4f3e533d9f975a081406f44813d08b83b2bc9021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87244e108e6a305d57f051de29d3f9ce02db12e50faf5e999c63daf79347e9f5 0.600000000000 1724875 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": 1237926, "vin": [ { "gen": { "height": 1237916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87244e108e6a305d57f051de29d3f9ce02db12e50faf5e999c63daf79347e9f5" } } ], "extra": [ 1, 102, 131, 247, 40, 40, 93, 79, 86, 236, 85, 94, 136, 173, 164, 243, 229, 51, 217, 249, 117, 160, 129, 64, 111, 68, 129, 61, 8, 184, 59, 43, 201, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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