← previous blocknext block →recent activity
Analyzing
Block #106,568,838
17 transactions · 16 stateful · 2026-09-20 21:19:57 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,568,838 · 17 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
1w02w13w24w25w39w010w114w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0463db49…5d05
0x34b655…2a6f
6 touches
3 conflicts
0xc1da8f73…484c
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x471f9f88…c6c8
0x34b655…2a6f
6 touches
3 conflicts
0x337c9d36…63a8
0x34b655…2a6f
4 touches
1 conflict
0x4542aadb…1cd2
0x34b655…2a6f
4 touches
1 conflict
0xfedc69b9…5d36
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
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
3 conflicts on slot 0x0463db492b…795d05
Audit this contract →
← previous block·next block →recent activity