Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4debc4052668f3cc5c7f3daacba6bd6f63f3d1dfb697bf2f33588f73a532a1f

Tx prefix hash: 2562e6dac3c0eb805bc3c5bc5e1169b7cb7dade90b9c8f455fee745569f77ae0
Tx public key: 7834c5efe65db7b694543f175113c5d7deb19b7eac1ce0f08f09dce2576caa46
Timestamp: 1696692694 Timestamp [UCT]: 2023-10-07 15:31:34 Age [y:d:h:m:s]: 01:091:12:31:42
Block: 864526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326681 RingCT/type: yes/0
Extra: 017834c5efe65db7b694543f175113c5d7deb19b7eac1ce0f08f09dce2576caa4602110000000d75e3f0e9000000000000000000

1 output(s) for total of 0.838429433000 dcy

stealth address amount amount idx
00: eaf3a0cffbc8d29fb4f3b101d18b7fec4cdae4ea8c44120ee5a02d4c56b21dd3 0.838429433000 1319042 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": 864536, "vin": [ { "gen": { "height": 864526 } } ], "vout": [ { "amount": 838429433, "target": { "key": "eaf3a0cffbc8d29fb4f3b101d18b7fec4cdae4ea8c44120ee5a02d4c56b21dd3" } } ], "extra": [ 1, 120, 52, 197, 239, 230, 93, 183, 182, 148, 84, 63, 23, 81, 19, 197, 215, 222, 177, 155, 126, 172, 28, 224, 240, 143, 9, 220, 226, 87, 108, 170, 70, 2, 17, 0, 0, 0, 13, 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