Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d36c3e09c60fe18ed9111b7d54cda5c23cbbf7f5a08160951a8f17de0648bc3

Tx prefix hash: bebd29d06b07f9f12b8f8fe569a4485a176cfe660edbde4ab4c77e6aea1c18b7
Tx public key: b88af95c7adb866a56a995973e5a89acf5afd8457dfac8f03ad7475c84d3a9ac
Timestamp: 1724221040 Timestamp [UCT]: 2024-08-21 06:17:20 Age [y:d:h:m:s]: 00:244:01:37:43
Block: 1092560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174301 RingCT/type: yes/0
Extra: 01b88af95c7adb866a56a995973e5a89acf5afd8457dfac8f03ad7475c84d3a9ac021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49279b0614db4f9735f2ed4f1419b84b24ff488fc501e35e2bf34a811517d802 0.600000000000 1567329 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": 1092570, "vin": [ { "gen": { "height": 1092560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49279b0614db4f9735f2ed4f1419b84b24ff488fc501e35e2bf34a811517d802" } } ], "extra": [ 1, 184, 138, 249, 92, 122, 219, 134, 106, 86, 169, 149, 151, 62, 90, 137, 172, 245, 175, 216, 69, 125, 250, 200, 240, 58, 215, 71, 92, 132, 211, 169, 172, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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