← previous blocknext block →recent activity
Analyzing
Block #106,568,622
25 transactions · 21 stateful · 2026-09-20 21:18:52 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.48
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,568,622 · 25 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
1w04w16w011w012w213w114w116w320w422w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x4089d428…b018
0x34b655…2a6f
6 touches
3 conflicts
0x29fd1ca5…a88a
0x34b655…2a6f
4 touches
1 conflict
0xd8ca1bc1…cbcc
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5e8
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x742436a7…c4d4
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity