← previous blocknext block →recent activity
Analyzing
Block #106,917,772
29 transactions · 29 stateful · 2026-09-22 02:37:11 UTC
Parallelism
45/100
Blocked
66%
Avg conflicts / tx
2.62
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,917,772 · 29 txs across 16 waves · depth 16
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
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w26w38w09w110w211w312w413w514w615w116w717w818w919w1020w1121w1226w1327w1428w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd192f4ed…d7ec
0x34b655…2a6f
18 touches
36 conflicts
0x51087f5a…61f7
0x34b655…2a6f
16 touches
28 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
14 touches
21 conflicts
0x93e4c736…3731
0x34b655…2a6f
14 touches
21 conflicts
0xe6c1556a…9284
0x34b655…2a6f
14 touches
21 conflicts
0x42522e76…2592
0x34b655…2a6f
14 touches
21 conflicts
0xcfb1298a…89f3
0x34b655…2a6f
10 touches
10 conflicts
0x518221db…65f7
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
36 conflicts on slot 0xd192f4edae…03d7ec
Audit this contract →
← previous block·next block →recent activity