← previous blocknext block →recent activity
Analyzing
Block #93,576,304
10 transactions · 10 stateful · 2026-08-06 07:41:09 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,576,304 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0xf43702bf…9e69
0x065c9d…c394
3 touches
1 conflict
0x7982638b…f9b7
0x065c9d…c394
3 touches
1 conflict
0x3aa6f2e0…0c54
0x065c9d…c394
2 touches
0 conflicts
0xa50c55b8…40d8
0x065c9d…c394
2 touches
0 conflicts
0xbc864c6f…84be
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x9ff176a9ad…67152e
Audit this contract →
← previous block·next block →recent activity