Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a443d1ad4cfbb4d233de6c1a11f1abe4d7aaf054505a713383b3494cc455ae91

Tx prefix hash: 6df1bd799e31d7c1e449fb2fd11cfc3e07a7b53d8eee874fb600a9e4f0087325
Tx public key: 5eeb82406cb8730d9d5c6761023b4b459a346555071c579e8873af91669a35d3
Timestamp: 1696922910 Timestamp [UCT]: 2023-10-10 07:28:30 Age [y:d:h:m:s]: 01:090:06:49:56
Block: 866439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325778 RingCT/type: yes/0
Extra: 015eeb82406cb8730d9d5c6761023b4b459a346555071c579e8873af91669a35d3021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.836021348000 dcy

stealth address amount amount idx
00: 511683fe3f79281f892bb840624fcd58e05d41fdb124912dd38489008e64a434 0.836021348000 1321031 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": 866449, "vin": [ { "gen": { "height": 866439 } } ], "vout": [ { "amount": 836021348, "target": { "key": "511683fe3f79281f892bb840624fcd58e05d41fdb124912dd38489008e64a434" } } ], "extra": [ 1, 94, 235, 130, 64, 108, 184, 115, 13, 157, 92, 103, 97, 2, 59, 75, 69, 154, 52, 101, 85, 7, 28, 87, 158, 136, 115, 175, 145, 102, 154, 53, 211, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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