Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3da46a6edf4e35379fcd223beef7d1fede46aad5fc7e0007182fe14ae24321ea

Tx prefix hash: 0c28159b5a1a2331ce7a3b1e0a7285b4625c642631e0f8d6944591a1142a20f6
Tx public key: eaa379686d8702cc8c6da53012e3fc72e826f910281ce5f704108735aa9862dd
Timestamp: 1682818444 Timestamp [UCT]: 2023-04-30 01:34:04 Age [y:d:h:m:s]: 01:344:04:48:51
Block: 749555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507234 RingCT/type: yes/0
Extra: 01eaa379686d8702cc8c6da53012e3fc72e826f910281ce5f704108735aa9862dd021100000002b3164c24000000000000000000

1 output(s) for total of 2.015641696000 dcy

stealth address amount amount idx
00: 079a85fd0efadfaf1d84634737a5b18b289ce81ab30ccac3590d4fc0faa6f525 2.015641696000 1197536 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": 749565, "vin": [ { "gen": { "height": 749555 } } ], "vout": [ { "amount": 2015641696, "target": { "key": "079a85fd0efadfaf1d84634737a5b18b289ce81ab30ccac3590d4fc0faa6f525" } } ], "extra": [ 1, 234, 163, 121, 104, 109, 135, 2, 204, 140, 109, 165, 48, 18, 227, 252, 114, 232, 38, 249, 16, 40, 28, 229, 247, 4, 16, 135, 53, 170, 152, 98, 221, 2, 17, 0, 0, 0, 2, 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