← previous blocknext block →recent activity
Analyzing
Block #106,917,334
21 transactions · 20 stateful · 2026-09-22 02:34:59 UTC
Parallelism
48/100
Blocked
50%
Avg conflicts / tx
1.67
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,917,334 · 21 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w411w512w613w714w815w916w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70986451…c6bd
0x34b655…2a6f
14 touches
21 conflicts
0x251ee419…4404
0x34b655…2a6f
12 touches
15 conflicts
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
12 touches
15 conflicts
0xc7ce92b1…25d0
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x1d02654c…ff86
0x34b655…2a6f
4 touches
1 conflict
0x53ca1284…cb2c
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
21 conflicts on slot 0x7098645134…3ac6bd
Audit this contract →
← previous block·next block →recent activity