← previous blocknext block →recent activity
Analyzing
Block #106,535,828
18 transactions · 17 stateful · 2026-09-20 18:33:50 UTC
Parallelism
61/100
Blocked
53%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,535,828 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w16w19w210w111w312w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07c47b1c…93c8
0x34b655…2a6f
14 touches
21 conflicts
0xba65d335…5a78
0x34b655…2a6f
14 touches
21 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
8 touches
6 conflicts
0x524f0872…0d12
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x26677a9c…3da5
0x34b655…2a6f
4 touches
1 conflict
0x3b6e959d…158f
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
21 conflicts on slot 0x07c47b1ce2…b693c8
Audit this contract →
← previous block·next block →recent activity