← previous blocknext block →recent activity
Analyzing
Block #106,253,237
32 transactions · 29 stateful · 2026-09-19 18:51:37 UTC
Parallelism
81/100
Blocked
59%
Avg conflicts / tx
1.16
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,253,237 · 32 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w15w27w08w09w111w213w315w016w117w218w319w428w129w430w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2642468f…6d81
0x34b655…2a6f
10 touches
10 conflicts
0x345b6a56…6e3f
0x34b655…2a6f
10 touches
10 conflicts
0x366a19b0…f065
0x34b655…2a6f
10 touches
10 conflicts
0x4ef288eb…015a
0x34b655…2a6f
10 touches
10 conflicts
0x6ca407b4…1edc
0x34b655…2a6f
10 touches
10 conflicts
0x75f928fc…0465
0x34b655…2a6f
10 touches
10 conflicts
0x839c0c71…bada
0x34b655…2a6f
10 touches
10 conflicts
0x85a88798…f85e
0x34b655…2a6f
10 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
10 conflicts on slot 0x2642468f6b…406d81
Audit this contract →
← previous block·next block →recent activity