Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad5362dcb7f09c5c40add30d6f958e7570245df04f85fb6720a18c1b380fb5e0

Tx prefix hash: f337efe7cc5413f49cd9212de66434a5633e75360a98a90022bf2ad4059d85b7
Tx public key: d3e3341af20fd582cc07d007eb9b8d0ed60d3954f25315fa8ba40ca893c9dee9
Timestamp: 1722809290 Timestamp [UCT]: 2024-08-04 22:08:10 Age [y:d:h:m:s]: 01:095:15:50:00
Block: 1080840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326851 RingCT/type: yes/0
Extra: 01d3e3341af20fd582cc07d007eb9b8d0ed60d3954f25315fa8ba40ca893c9dee9021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f2e1b57f3f0d173267d6e1511dbce73992cdad200d1b298665f7648bc472b37 0.600000000000 1554355 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": 1080850, "vin": [ { "gen": { "height": 1080840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f2e1b57f3f0d173267d6e1511dbce73992cdad200d1b298665f7648bc472b37" } } ], "extra": [ 1, 211, 227, 52, 26, 242, 15, 213, 130, 204, 7, 208, 7, 235, 155, 141, 14, 214, 13, 57, 84, 242, 83, 21, 250, 139, 164, 12, 168, 147, 201, 222, 233, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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