← previous blocknext block →recent activity
Analyzing
Block #106,551,617
18 transactions · 17 stateful · 2026-09-20 19:53:17 UTC
Parallelism
61/100
Blocked
71%
Avg conflicts / tx
2.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,551,617 · 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
1w02w13w24w05w16w17w28w29w310w411w512w617w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07c47b1c…93c8
0x34b655…2a6f
14 touches
21 conflicts
0xe530b2cf…6f95
0x34b655…2a6f
12 touches
15 conflicts
0xc1da8f73…484c
0x34b655…2a6f
8 touches
6 conflicts
0x69411fb3…e36d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x17a7f697…dcb6
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x4651a877…25a1
0x34b655…2a6f
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
21 conflicts on slot 0x07c47b1ce2…b693c8
Audit this contract →
← previous block·next block →recent activity