← previous blocknext block →recent activity
Analyzing
Block #108,988,703
20 transactions · 17 stateful · 2026-09-29 08:28:29 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,988,703 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w29w010w113w214w317w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05e92091…487b
0x34b655…2a6f
6 touches
3 conflicts
0x2bd71786…2d83
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x6235638c…643c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
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
3 conflicts on slot 0x05e92091d0…9d487b
Audit this contract →
← previous block·next block →recent activity