Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42c7922d31271cfb002302a7294189d48fe7f82a8fd472dbceb56b748949688a

Tx prefix hash: 5727258a1ce099fb17427d699acdc90bcd97c45f5b97f985ce82159aa3179261
Tx public key: e729e89a81d4757a2398b2a4fc6a066f2898e67082dc34d586b4b367113fe301
Timestamp: 1682385319 Timestamp [UCT]: 2023-04-25 01:15:19 Age [y:d:h:m:s]: 02:038:13:50:15
Block: 745960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 549745 RingCT/type: yes/0
Extra: 01e729e89a81d4757a2398b2a4fc6a066f2898e67082dc34d586b4b367113fe301021100000001b3164c24000000000000000000

1 output(s) for total of 2.071691415000 dcy

stealth address amount amount idx
00: 07276e0fbe0a619bca33ebdd195a0fa216c7b7c0005df4b40e06a529a0865439 2.071691415000 1193461 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": 745970, "vin": [ { "gen": { "height": 745960 } } ], "vout": [ { "amount": 2071691415, "target": { "key": "07276e0fbe0a619bca33ebdd195a0fa216c7b7c0005df4b40e06a529a0865439" } } ], "extra": [ 1, 231, 41, 232, 154, 129, 212, 117, 122, 35, 152, 178, 164, 252, 106, 6, 111, 40, 152, 230, 112, 130, 220, 52, 213, 134, 180, 179, 103, 17, 63, 227, 1, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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