Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 329d16fa1f0c1cc8b6794d7d39c41921d77e64ff0fbc7f99c2927172c390c899

Tx prefix hash: 23cae54168b81937bb5162c2c89a5f3b54b939995d75ff8339731a8f3c773350
Tx public key: a3ac86f8b7dcfdcc7842cde4a986a2e6330841eac6655e3b967d19b4b96bda5f
Timestamp: 1732000180 Timestamp [UCT]: 2024-11-19 07:09:40 Age [y:d:h:m:s]: 00:005:04:01:22
Block: 1156957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3688 RingCT/type: yes/0
Extra: 01a3ac86f8b7dcfdcc7842cde4a986a2e6330841eac6655e3b967d19b4b96bda5f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dbe6a8a486c79029c876ac0b650684d9c6f21b332a35fcf9454826af4130cb3 0.600000000000 1642580 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": 1156967, "vin": [ { "gen": { "height": 1156957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dbe6a8a486c79029c876ac0b650684d9c6f21b332a35fcf9454826af4130cb3" } } ], "extra": [ 1, 163, 172, 134, 248, 183, 220, 253, 204, 120, 66, 205, 228, 169, 134, 162, 230, 51, 8, 65, 234, 198, 101, 94, 59, 150, 125, 25, 180, 185, 107, 218, 95, 2, 17, 0, 0, 0, 3, 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