Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef3f88a849e9d56de9e78c1fa9ce84928d7b4c985ecc0321f479be5a9594f830

Tx prefix hash: da115309641e9a9697299f33714738c92855b7d9ea531df3bfbc9e800c99b354
Tx public key: 240b94a751d95ebf8ceedd7a03edb1e5a3d082ab16a0a32c9fb5f6244e03ab29
Timestamp: 1736341216 Timestamp [UCT]: 2025-01-08 13:00:16 Age [y:d:h:m:s]: 00:105:19:56:38
Block: 1192893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75439 RingCT/type: yes/0
Extra: 01240b94a751d95ebf8ceedd7a03edb1e5a3d082ab16a0a32c9fb5f6244e03ab29021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21525e1e3d51c435de305ea657d97f1c106e015b185db3281225d64cfa4ee97d 0.600000000000 1679450 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": 1192903, "vin": [ { "gen": { "height": 1192893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21525e1e3d51c435de305ea657d97f1c106e015b185db3281225d64cfa4ee97d" } } ], "extra": [ 1, 36, 11, 148, 167, 81, 217, 94, 191, 140, 238, 221, 122, 3, 237, 177, 229, 163, 208, 130, 171, 22, 160, 163, 44, 159, 181, 246, 36, 78, 3, 171, 41, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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