← previous blocknext block →recent activity
Analyzing
Block #107,849,104
24 transactions · 23 stateful · 2026-09-25 08:47:22 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,849,104 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w110w011w113w114w015w116w217w318w419w520w222w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba522812…1f1f
0x34b655…2a6f
8 touches
6 conflicts
0x981254c6…2e26
0x34b655…2a6f
8 touches
6 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x62030a81…91be
0x34b655…2a6f
4 touches
1 conflict
0x711ceb8d…5202
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
6 conflicts on slot 0xba52281226…3a1f1f
Audit this contract →
← previous block·next block →recent activity