Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f024a0c26486c7f8b95c29a85644504e3a89a6a41eb052a1e0a4573f3eed2a1

Tx prefix hash: 3faa88146cdf752940b54a9ea2035b7421fffaa921d41c0e654d8e35e6b4eda1
Tx public key: 5d7747dae3c707e9ff09b115fa4b656314db3a150aa8cb7f0f1f2ea69ae45f67
Timestamp: 1702557652 Timestamp [UCT]: 2023-12-14 12:40:52 Age [y:d:h:m:s]: 01:134:23:17:59
Block: 912945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357625 RingCT/type: yes/0
Extra: 015d7747dae3c707e9ff09b115fa4b656314db3a150aa8cb7f0f1f2ea69ae45f6702110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61ae3c2bc7b0783f65fe0de797f36b88cc18d9c718b24106e32cef9a33537368 0.600000000000 1370181 of 15

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": 912955, "vin": [ { "gen": { "height": 912945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61ae3c2bc7b0783f65fe0de797f36b88cc18d9c718b24106e32cef9a33537368" } } ], "extra": [ 1, 93, 119, 71, 218, 227, 199, 7, 233, 255, 9, 177, 21, 250, 75, 101, 99, 20, 219, 58, 21, 10, 168, 203, 127, 15, 31, 46, 166, 154, 228, 95, 103, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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