Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bf9a3171df2f11e5193d62837c85cb44245a9637b2a9bfa4732187c19e6a99f

Tx prefix hash: 5b39986d8a228497ae8abba0e93572f8519bf2ea22c067364d98f412dcee15c9
Tx public key: fe1683f6daa1c34cade1a74e187903a3cb63896e1c22253e74fc47fa6f9f842c
Timestamp: 1711445964 Timestamp [UCT]: 2024-03-26 09:39:24 Age [y:d:h:m:s]: 01:072:07:52:44
Block: 986663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312682 RingCT/type: yes/0
Extra: 01fe1683f6daa1c34cade1a74e187903a3cb63896e1c22253e74fc47fa6f9f842c021100000002a162b83d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b42730c821343329c7adb59af9c4f64483af30a15e91eee71cf64ca8ab3da7c 0.600000000000 1446896 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": 986673, "vin": [ { "gen": { "height": 986663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b42730c821343329c7adb59af9c4f64483af30a15e91eee71cf64ca8ab3da7c" } } ], "extra": [ 1, 254, 22, 131, 246, 218, 161, 195, 76, 173, 225, 167, 78, 24, 121, 3, 163, 203, 99, 137, 110, 28, 34, 37, 62, 116, 252, 71, 250, 111, 159, 132, 44, 2, 17, 0, 0, 0, 2, 161, 98, 184, 61, 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