← previous blocknext block →recent activity
Analyzing
Block #106,389,182
37 transactions · 32 stateful · 2026-09-20 06:15:44 UTC
Parallelism
60/100
Blocked
59%
Avg conflicts / tx
2.22
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,389,182 · 37 txs across 15 waves · depth 15
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
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w48w120w222w325w726w827w928w1029w1130w1131w1232w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x168458e1…ca7e
0x34b655…2a6f
16 touches
28 conflicts
0x9dd1656a…dca5
0x34b655…2a6f
14 touches
21 conflicts
0xba33378a…f1df
0x34b655…2a6f
12 touches
15 conflicts
0xac0b4a08…faae
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x0eb80b70…301b
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
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 0x168458e176…45ca7e
Audit this contract →
← previous block·next block →recent activity