← previous blocknext block →recent activity
Analyzing
Block #107,849,056
18 transactions · 17 stateful · 2026-09-25 08:47:07 UTC
Parallelism
83/100
Blocked
24%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #107,849,056 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w012w113w216w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf75c3a6b…0568
0x34b655…2a6f
6 touches
3 conflicts
0x0b223a4f…8fe0
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x5d0647dc…6034
0x34b655…2a6f
4 touches
1 conflict
0x7bd229ad…63b2
0x34b655…2a6f
4 touches
1 conflict
0x92132ed7…2722
0x34b655…2a6f
4 touches
1 conflict
0xa69bb4e1…f2bb
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
3 conflicts on slot 0xf75c3a6bf5…da0568
Audit this contract →
← previous block·next block →recent activity