← previous blocknext block →recent activity
Analyzing
Block #106,272,126
28 transactions · 25 stateful · 2026-09-19 20:26:40 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,272,126 · 28 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
1w02w13w14w26w018w219w322w023w125w026w127w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x976029c0…a4de
0x34b655…2a6f
8 touches
6 conflicts
0x719e7a70…cd01
0x34b655…2a6f
8 touches
6 conflicts
0x86cea35b…bdff
0x34b655…2a6f
8 touches
6 conflicts
0x3b6e959d…158f
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x4b8cca0a…87fe
0x34b655…2a6f
4 touches
1 conflict
0x9430e759…86df
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 0x976029c05b…f4a4de
Audit this contract →
← previous block·next block →recent activity