← previous blocknext block →recent activity
Analyzing
Block #107,816,372
30 transactions · 23 stateful · 2026-09-25 06:02:37 UTC
Parallelism
63/100
Blocked
52%
Avg conflicts / tx
1.4
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #107,816,372 · 30 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w012w113w214w315w416w517w618w719w820w921w1029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7679110…572d
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x72083f0d…082a
0x34b655…2a6f
8 touches
6 conflicts
0x2b856d86…7988
0x34b655…2a6f
8 touches
6 conflicts
0x2328941c…84d3
0x34b655…2a6f
8 touches
6 conflicts
0xab0c9ca9…926b
0x34b655…2a6f
8 touches
6 conflicts
0xc0893415…913d
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xc7679110cf…22572d
Audit this contract →
← previous block·next block →recent activity