← previous blocknext block →recent activity
Analyzing
Block #107,849,144
20 transactions · 19 stateful · 2026-09-25 08:47:34 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,849,144 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf75c3a6b…0568
0x34b655…2a6f
8 touches
6 conflicts
0xee757899…302b
0x34b655…2a6f
4 touches
1 conflict
0x1667c89c…725c
0x34b655…2a6f
4 touches
1 conflict
0x9ad325f5…cc43
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x62811193…186a
0x34ae4d…3fc5
2 touches
0 conflicts
0x7a89325a…d7e0
0x34ae4d…3fc5
2 touches
0 conflicts
0xd671bc34…553c
0x34ae4d…3fc5
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
6 conflicts on slot 0xf75c3a6bf5…da0568
Audit this contract →
← previous block·next block →recent activity