← previous blocknext block →recent activity
Analyzing
Block #106,199,258
19 transactions · 19 stateful · 2026-09-19 14:19:51 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,199,258 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w29w110w211w312w213w314w417w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ed92b3f…20ea
0x34b655…2a6f
10 touches
10 conflicts
0xf195ad96…e0c3
0x34b655…2a6f
8 touches
6 conflicts
0x5717771c…45ed
0x34b655…2a6f
6 touches
3 conflicts
0xcfe180d7…b5a4
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
6 touches
3 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
10 conflicts on slot 0x8ed92b3f48…e020ea
Audit this contract →
← previous block·next block →recent activity