← previous blocknext block →recent activity
Analyzing
Block #107,788,472
11 transactions · 11 stateful · 2026-09-25 03:42:06 UTC
Parallelism
55/100
Blocked
36%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,788,472 · 11 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w27w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xea3ca8da…fbd2
0x34b655…2a6f
4 touches
1 conflict
0x4e63e094…ea93
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x42744667…0b8a
0x34b655…2a6f
2 touches
0 conflicts
0x45298602…0f79
0x34b655…2a6f
2 touches
0 conflicts
0x51d95405…ebd5
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity