Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c38dda6335444c296b3871da8cfc14182535e05f430a5e08f5f3a9710c514be

Tx prefix hash: d9886b3ba74d4ea8b16e6241e6f603cd27bb76084134340302cb0ded1b45f847
Tx public key: e5f4a22879c74226bab7bc718956f81b66412b285a7a88f9a336f3b52782e03c
Timestamp: 1715947644 Timestamp [UCT]: 2024-05-17 12:07:24 Age [y:d:h:m:s]: 00:239:03:39:48
Block: 1023961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171162 RingCT/type: yes/0
Extra: 01e5f4a22879c74226bab7bc718956f81b66412b285a7a88f9a336f3b52782e03c021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b737f64bf8234341b63a2a9b9cc07cbf707daf792655f2607dbf769c15503b68 0.600000000000 1489334 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": 1023971, "vin": [ { "gen": { "height": 1023961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b737f64bf8234341b63a2a9b9cc07cbf707daf792655f2607dbf769c15503b68" } } ], "extra": [ 1, 229, 244, 162, 40, 121, 199, 66, 38, 186, 183, 188, 113, 137, 86, 248, 27, 102, 65, 43, 40, 90, 122, 136, 249, 163, 54, 243, 181, 39, 130, 224, 60, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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