Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92d3ba9be4e0a9acb9196e4e451624700d54a2eae9740cef67ce7a50958e13f3

Tx prefix hash: ffd31b7b5a97608c05180c3c14b3e7125e7aa2c84c258e056ad5879bf0c9c413
Tx public key: 202e0320e0b3cd794b2b25d0fef0d55afd39623535dcebb4efc164db12f46841
Timestamp: 1749335471 Timestamp [UCT]: 2025-06-07 22:31:11 Age [y:d:h:m:s]: 00:156:06:11:43
Block: 1300208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109351 RingCT/type: yes/0
Extra: 01202e0320e0b3cd794b2b25d0fef0d55afd39623535dcebb4efc164db12f46841021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d566d50ada4f18f5d9412bd197eb607d68840c4b7e0890533105cf2cce73c9e 0.600000000000 1787757 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": 1300218, "vin": [ { "gen": { "height": 1300208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d566d50ada4f18f5d9412bd197eb607d68840c4b7e0890533105cf2cce73c9e" } } ], "extra": [ 1, 32, 46, 3, 32, 224, 179, 205, 121, 75, 43, 37, 208, 254, 240, 213, 90, 253, 57, 98, 53, 53, 220, 235, 180, 239, 193, 100, 219, 18, 244, 104, 65, 2, 17, 0, 0, 0, 2, 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