Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79cb700f49f308377161504a3f166157222801971700252e504aa76b69c87866

Tx prefix hash: eba22e75ef69a8d1656a16d43dcba924774fd8555009636852b7a2bfd024f7fb
Tx public key: 8e1d87c1654e1d7829e73c73bc0d749fc45ea7abaf5189e390e290e5d17d07c4
Timestamp: 1697698674 Timestamp [UCT]: 2023-10-19 06:57:54 Age [y:d:h:m:s]: 01:175:12:36:27
Block: 872864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386483 RingCT/type: yes/0
Extra: 018e1d87c1654e1d7829e73c73bc0d749fc45ea7abaf5189e390e290e5d17d07c402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.786754522000 dcy

stealth address amount amount idx
00: 0240f7944e704c5991d1c687551c99a5ff7f9eeb07ec3df41751238131b96a75 0.786754522000 1327972 of 0

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": 872874, "vin": [ { "gen": { "height": 872864 } } ], "vout": [ { "amount": 786754522, "target": { "key": "0240f7944e704c5991d1c687551c99a5ff7f9eeb07ec3df41751238131b96a75" } } ], "extra": [ 1, 142, 29, 135, 193, 101, 78, 29, 120, 41, 231, 60, 115, 188, 13, 116, 159, 196, 94, 167, 171, 175, 81, 137, 227, 144, 226, 144, 229, 209, 125, 7, 196, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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