← previous blocknext block →recent activity
Analyzing
Block #107,990,253
19 transactions · 15 stateful · 2026-09-25 20:37:55 UTC
Parallelism
84/100
Blocked
20%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #107,990,253 · 19 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
5w07w111w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9047e17d…1be8
0x34b655…2a6f
4 touches
1 conflict
0xdabae01b…82be
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x51e96b98…de36
0x34b655…2a6f
4 touches
1 conflict
0x6293016e…b6a7
0x34b655…2a6f
4 touches
1 conflict
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0x01a89030…f786
0x98dc6e…8633
2 touches
0 conflicts
0x0fc41e7b…6831
0x98dc6e…8633
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
1 conflict on slot 0x9047e17d5b…f01be8
Audit this contract →
← previous block·next block →recent activity