← previous blocknext block →recent activity
Analyzing
Block #106,372,574
23 transactions · 22 stateful · 2026-09-20 04:52:09 UTC
Parallelism
57/100
Blocked
59%
Avg conflicts / tx
2.17
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,372,574 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w110w212w213w314w416w417w518w619w720w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b25f260…c429
0x34b655…2a6f
14 touches
21 conflicts
0x8d664414…3344
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xfdd815a5…75c9
0x34b655…2a6f
8 touches
6 conflicts
0x0f270a31…640c
0x34b655…2a6f
8 touches
6 conflicts
0x9c2fc330…0091
0x34b655…2a6f
8 touches
6 conflicts
0xcc9bc5e3…f916
0x34b655…2a6f
8 touches
6 conflicts
0xc6452476…a74a
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 0x1b25f26097…52c429
Audit this contract →
← previous block·next block →recent activity