← previous blocknext block →recent activity
Analyzing
Block #106,946,901
20 transactions · 19 stateful · 2026-09-22 05:03:48 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.3
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,946,901 · 20 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
1w02w13w04w06w17w28w312w014w115w416w517w618w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23d86357…aab1
0x34b655…2a6f
14 touches
21 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
10 touches
10 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x01ad5dd0…11a1
0x34b655…2a6f
6 touches
3 conflicts
0x9375a764…dca1
0x34b655…2a6f
6 touches
3 conflicts
0x155e52ca…fac7
0x34b655…2a6f
6 touches
3 conflicts
0x962db0c5…b55e
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 0x23d8635733…f2aab1
Audit this contract →
← previous block·next block →recent activity