← previous blocknext block →recent activity
Analyzing
Block #106,921,527
38 transactions · 36 stateful · 2026-09-22 02:56:05 UTC
Parallelism
66/100
Blocked
64%
Avg conflicts / tx
1.97
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,921,527 · 38 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w17w28w39w415w016w217w318w419w520w626w1228w230w233w535w736w837w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba1edffb…323e
0x34b655…2a6f
16 touches
28 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
14 touches
21 conflicts
0xf7ae2120…d1d2
0x34b655…2a6f
12 touches
15 conflicts
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x7a43e31a…3cb5
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7bd708f1…f775
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0xba1edffb42…64323e
Audit this contract →
← previous block·next block →recent activity