Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adb6e0d21e7f1e512f1108125e854ab2ed11d18d91b09e196c2a86a1d834a4e2

Tx prefix hash: 470227a40d66530bb71fb4d4f7af0b57dd4ca69ee30647d6277678b278a75556
Tx public key: f84496d844924a014afecd52576aa073eefbb4fb263a57d48aad8403342a9b2a
Timestamp: 1726644154 Timestamp [UCT]: 2024-09-18 07:22:34 Age [y:d:h:m:s]: 00:071:03:57:37
Block: 1112637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50877 RingCT/type: yes/0
Extra: 01f84496d844924a014afecd52576aa073eefbb4fb263a57d48aad8403342a9b2a021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f94a0b3c9317fb72ed8531128499e3c119461d399bf0e35d08675bb925560c00 0.600000000000 1592028 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": 1112647, "vin": [ { "gen": { "height": 1112637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f94a0b3c9317fb72ed8531128499e3c119461d399bf0e35d08675bb925560c00" } } ], "extra": [ 1, 248, 68, 150, 216, 68, 146, 74, 1, 74, 254, 205, 82, 87, 106, 160, 115, 238, 251, 180, 251, 38, 58, 87, 212, 138, 173, 132, 3, 52, 42, 155, 42, 2, 17, 0, 0, 0, 4, 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