← previous blocknext block →recent activity
Analyzing
Block #106,922,082
30 transactions · 29 stateful · 2026-09-22 02:58:53 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,922,082 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w010w112w213w014w115w216w217w318w419w521w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecd87a39…d9c5
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x6cf9c605…7b8f
0x34b655…2a6f
8 touches
6 conflicts
0x51087f5a…61f7
0x34b655…2a6f
8 touches
6 conflicts
0x93e4c736…3731
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x42522e76…2592
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
10 conflicts on slot 0xecd87a399c…10d9c5
Audit this contract →
← previous block·next block →recent activity