Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9db12c6f7d1314a1e8e3513097a97509b771829fa8c224827a5fa4b3a07b20ec

Tx prefix hash: ad83d80121ab5f4d56cd947163f2d08c72b390350d9fcadfa901dba48365ce1d
Tx public key: f7d0d3f3df7afb853870aaa04ec1589bdd77d1ff7819b8d02c1a1901a8f93906
Timestamp: 1737972616 Timestamp [UCT]: 2025-01-27 10:10:16 Age [y:d:h:m:s]: 00:046:05:52:41
Block: 1206159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33073 RingCT/type: yes/0
Extra: 01f7d0d3f3df7afb853870aaa04ec1589bdd77d1ff7819b8d02c1a1901a8f939060211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9b825cdd656bef2a192684ddca6f71e6fe39bc451234fb73b4230bf2d127350 0.600000000000 1692862 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": 1206169, "vin": [ { "gen": { "height": 1206159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9b825cdd656bef2a192684ddca6f71e6fe39bc451234fb73b4230bf2d127350" } } ], "extra": [ 1, 247, 208, 211, 243, 223, 122, 251, 133, 56, 112, 170, 160, 78, 193, 88, 155, 221, 119, 209, 255, 120, 25, 184, 208, 44, 26, 25, 1, 168, 249, 57, 6, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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