← previous blocknext block →recent activity
Analyzing
Block #107,824,049
20 transactions · 19 stateful · 2026-09-25 06:41:16 UTC
Parallelism
60/100
Blocked
53%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,824,049 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w19w210w311w412w513w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xa7ba83b5…d0a8
0x34b655…2a6f
10 touches
10 conflicts
0x14fe1598…d0ba
0x34b655…2a6f
8 touches
6 conflicts
0x6dac76e3…04c9
0x34b655…2a6f
8 touches
6 conflicts
0x9ad325f5…cc43
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x25144f94…1854
0x34b655…2a6f
8 touches
6 conflicts
0x921a58d1…db22
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity