← previous blocknext block →recent activity
Analyzing
Block #107,814,322
28 transactions · 19 stateful · 2026-09-25 05:52:18 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.64
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,814,322 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w19w011w012w113w214w315w417w518w627w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa23b9051…392f
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x2ea3a28c…c266
0x34b655…2a6f
6 touches
3 conflicts
0xaae6463e…bfcc
0x34b655…2a6f
6 touches
3 conflicts
0xdeaa385f…6b8b
0x34b655…2a6f
6 touches
3 conflicts
0xb34613e3…a365
0x34b655…2a6f
6 touches
3 conflicts
0xbb96f8af…205f
0x34b655…2a6f
4 touches
1 conflict
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 0xa23b905120…88392f
Audit this contract →
← previous block·next block →recent activity