← previous blocknext block →recent activity
Analyzing
Block #106,430,985
19 transactions · 17 stateful · 2026-09-20 09:46:07 UTC
Parallelism
63/100
Blocked
41%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,430,985 · 19 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
3w04w110w113w214w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xdeb47041…03b5
0x34b655…2a6f
12 touches
15 conflicts
0xba33378a…f1df
0x34b655…2a6f
10 touches
10 conflicts
0x9a8482cc…8bee
0x34b655…2a6f
8 touches
6 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
6 touches
3 conflicts
0x168458e1…ca7e
0x34b655…2a6f
6 touches
3 conflicts
0x22229acd…2272
0x34b655…2a6f
4 touches
1 conflict
0x245a78ab…06b1
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity