← previous blocknext block →recent activity
Analyzing
Block #108,508,750
23 transactions · 22 stateful · 2026-09-27 16:07:21 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,508,750 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w210w311w012w113w214w315w016w417w119w020w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x67d1be…196f
8 touches
6 conflicts
0x00000000…0003
0x0a4fcb…a602
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x2b936aa5…05e5
0x141b1d…9583
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x2b093939…9088
0x1b6862…e19c
8 touches
6 conflicts
0x104134b9…2d01
0xd32edf…ff58
7 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: 0x67d1be51…42196f
6 conflicts on slot 0x0000000000…000001
Audit this contract →
← previous block·next block →recent activity