Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ed885a6aaadd3aad330d1f66f7a115f5fedc745f85786b6c06cc918e30b54d0

Tx prefix hash: f6aede70a1fbdc98075e59b19241d516295fd4925ecae2e107c2645b724ab381
Tx public key: b35ac025cb37e9efa376378bace4c37354db6c5ab1d320b61a233f9348490fde
Timestamp: 1699101394 Timestamp [UCT]: 2023-11-04 12:36:34 Age [y:d:h:m:s]: 01:160:08:20:05
Block: 884536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375558 RingCT/type: yes/0
Extra: 01b35ac025cb37e9efa376378bace4c37354db6c5ab1d320b61a233f9348490fde02110000000833af99f4000000000000000000

1 output(s) for total of 0.719722450000 dcy

stealth address amount amount idx
00: aa48c2fd01e1959b52d2d28ea3aeba9dd4e679fc38788d0baa16d5b29a8b1708 0.719722450000 1340281 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": 884546, "vin": [ { "gen": { "height": 884536 } } ], "vout": [ { "amount": 719722450, "target": { "key": "aa48c2fd01e1959b52d2d28ea3aeba9dd4e679fc38788d0baa16d5b29a8b1708" } } ], "extra": [ 1, 179, 90, 192, 37, 203, 55, 233, 239, 163, 118, 55, 139, 172, 228, 195, 115, 84, 219, 108, 90, 177, 211, 32, 182, 26, 35, 63, 147, 72, 73, 15, 222, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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