Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 926ff6f2547a79605d575d4216eca21ae8e25e11e5069b14fb390b8e30bf2156

Tx prefix hash: 1f25b145ba432a93566bacdf8769f3a62ea4c0ac8dbd73f22dca5a92fd0f1dc3
Tx public key: 0e79fbfca6c483e940ad2b810e574e5b89aad30a74d9cc6a64f572e73e4e6f0d
Timestamp: 1749844778 Timestamp [UCT]: 2025-06-13 19:59:38 Age [y:d:h:m:s]: 00:153:10:10:34
Block: 1304345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107410 RingCT/type: yes/0
Extra: 010e79fbfca6c483e940ad2b810e574e5b89aad30a74d9cc6a64f572e73e4e6f0d021100000009bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43d018b9b2c55d30c9c58f60ab95080f54952b2b7f59b5434ffd64089e86c48e 0.600000000000 1791934 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": 1304355, "vin": [ { "gen": { "height": 1304345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43d018b9b2c55d30c9c58f60ab95080f54952b2b7f59b5434ffd64089e86c48e" } } ], "extra": [ 1, 14, 121, 251, 252, 166, 196, 131, 233, 64, 173, 43, 129, 14, 87, 78, 91, 137, 170, 211, 10, 116, 217, 204, 106, 100, 245, 114, 231, 62, 78, 111, 13, 2, 17, 0, 0, 0, 9, 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