← previous blocknext block →recent activity
Analyzing
Block #93,663,233
17 transactions · 17 stateful · 2026-08-06 14:58:10 UTC
Parallelism
59/100
Blocked
59%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,663,233 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w17w29w310w411w413w515w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98212952…9ba6
0x34b655…2a6f
10 touches
10 conflicts
0x310afe2c…83e1
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe4af4c87…9964
0x34b655…2a6f
6 touches
3 conflicts
0x15b47cb9…8bb7
0x34b655…2a6f
6 touches
3 conflicts
0xac101b79…270a
0x34b655…2a6f
6 touches
3 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: Perpl
10 conflicts on slot 0x982129521c…f19ba6
Audit this contract →
← previous block·next block →recent activity