← previous blocknext block →recent activity
Analyzing
Block #106,362,253
28 transactions · 27 stateful · 2026-09-20 04:00:12 UTC
Parallelism
75/100
Blocked
70%
Avg conflicts / tx
1.89
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,362,253 · 28 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
1w02w13w24w25w06w17w08w19w011w117w318w219w320w421w522w625w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x3934e758…1dea
0x34b655…2a6f
14 touches
21 conflicts
0xba33378a…f1df
0x34b655…2a6f
12 touches
15 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
10 touches
10 conflicts
0x2b5100fd…04e6
0x6f6493…b480
9 touches
10 conflicts
0x2c734a96…f823
0x6f6493…b480
9 touches
10 conflicts
0x3c051dff…3207
0x6f6493…b480
9 touches
10 conflicts
0x3e3e649a…53ed
0x6f6493…b480
9 touches
10 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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity