Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34fa07eac9dc829e917df4530632c21f60418fc809d82fd982b2111ecb446ab0

Tx prefix hash: e8c7c458eb5a0a95a55cce7f816c36ced8ff504a16464f21361756e6e4ab35dd
Tx public key: 520727ba4e1f895396c50e5ae0e536e255cabd74a2ac5f0e82e41253f887ad4f
Timestamp: 1711237181 Timestamp [UCT]: 2024-03-23 23:39:41 Age [y:d:h:m:s]: 01:083:23:15:32
Block: 984927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320908 RingCT/type: yes/0
Extra: 01520727ba4e1f895396c50e5ae0e536e255cabd74a2ac5f0e82e41253f887ad4f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7aa84ba2e395a488c11c51d6dfac55d72355bd09f0e0b4d73f7911001cf3243 0.600000000000 1445102 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": 984937, "vin": [ { "gen": { "height": 984927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7aa84ba2e395a488c11c51d6dfac55d72355bd09f0e0b4d73f7911001cf3243" } } ], "extra": [ 1, 82, 7, 39, 186, 78, 31, 137, 83, 150, 197, 14, 90, 224, 229, 54, 226, 85, 202, 189, 116, 162, 172, 95, 14, 130, 228, 18, 83, 248, 135, 173, 79, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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