← previous blocknext block →recent activity
Analyzing
Block #106,810,123
18 transactions · 13 stateful · 2026-09-21 17:35:20 UTC
Parallelism
78/100
Blocked
31%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,810,123 · 18 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
1w08w111w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe4dbfb0…c43c
0x34b655…2a6f
8 touches
6 conflicts
0x51087f5a…61f7
0x34b655…2a6f
6 touches
3 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xb46cf9e9…b932
0x34b655…2a6f
4 touches
1 conflict
0x01f19c33…170d
0x34b655…2a6f
4 touches
1 conflict
0x25957369…c648
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 0xbe4dbfb032…b6c43c
Audit this contract →
← previous block·next block →recent activity