Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73460b99043a458c0c4f523a978e2bac1223a89d4dae21a430cdb99f9684fe97

Tx prefix hash: 8e64f2a4162b42e3d88698c88e780233e32e9ef69bb7f8140c83ecbe6e705313
Tx public key: 0b16adf4e8d3a68d105e5c482e5fbce01b285c93fab5e08b3b5c08d423a941d8
Timestamp: 1674943704 Timestamp [UCT]: 2023-01-28 22:08:24 Age [y:d:h:m:s]: 01:295:10:07:59
Block: 684891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472097 RingCT/type: yes/0
Extra: 010b16adf4e8d3a68d105e5c482e5fbce01b285c93fab5e08b3b5c08d423a941d80211000000025029cbac000000000000000000

1 output(s) for total of 3.301199272000 dcy

stealth address amount amount idx
00: 358e88ddde48142e8661e8f0a4aa713aab243af683462ccec5d1d659ae0353c4 3.301199272000 1127170 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": 684901, "vin": [ { "gen": { "height": 684891 } } ], "vout": [ { "amount": 3301199272, "target": { "key": "358e88ddde48142e8661e8f0a4aa713aab243af683462ccec5d1d659ae0353c4" } } ], "extra": [ 1, 11, 22, 173, 244, 232, 211, 166, 141, 16, 94, 92, 72, 46, 95, 188, 224, 27, 40, 92, 147, 250, 181, 224, 139, 59, 92, 8, 212, 35, 169, 65, 216, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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