← previous blocknext block →recent activity
Analyzing
Block #105,933,010
12 transactions · 11 stateful · 2026-09-18 15:59:44 UTC
Parallelism
50/100
Blocked
64%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,933,010 · 12 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w36w07w110w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe796f8b7…ad55
0x34b655…2a6f
8 touches
6 conflicts
0xdd14b7c0…044f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x7dd96c96…7335
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xe796f8b7af…c7ad55
Audit this contract →
← previous block·next block →recent activity