Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 245fc3689cfaa788a44c26257930151fa9dc164b3bfa3a872fb2771c02247a17

Tx prefix hash: a0fbc2e939c4b05b9cc6dd0ba631e0294d9f58a995782a32a7140b8da89af31e
Tx public key: 89787f957cfdfc5f0ec51c941c9e44f877a260c41db553d6d9bdd49d33a9965c
Timestamp: 1724045077 Timestamp [UCT]: 2024-08-19 05:24:37 Age [y:d:h:m:s]: 00:225:21:50:18
Block: 1091100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161306 RingCT/type: yes/0
Extra: 0189787f957cfdfc5f0ec51c941c9e44f877a260c41db553d6d9bdd49d33a9965c02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec4479452ad6c987f35cba0a3a3f6fdef9b1a82331ba838f35dca68fe790178e 0.600000000000 1565725 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": 1091110, "vin": [ { "gen": { "height": 1091100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec4479452ad6c987f35cba0a3a3f6fdef9b1a82331ba838f35dca68fe790178e" } } ], "extra": [ 1, 137, 120, 127, 149, 124, 253, 252, 95, 14, 197, 28, 148, 28, 158, 68, 248, 119, 162, 96, 196, 29, 181, 83, 214, 217, 189, 212, 157, 51, 169, 150, 92, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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