← previous blocknext block →recent activity
Analyzing
Block #106,428,458
30 transactions · 28 stateful · 2026-09-20 09:33:23 UTC
Parallelism
87/100
Blocked
43%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,428,458 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w27w010w117w018w119w220w321w123w124w225w226w228w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6650a74…44b9
0x34b655…2a6f
8 touches
6 conflicts
0xa8590d68…d5c8
0x34b655…2a6f
8 touches
6 conflicts
0xa0685f64…f220
0x34b655…2a6f
8 touches
6 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
6 touches
3 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
6 touches
3 conflicts
0x5b17b0ae…fccf
0x34b655…2a6f
6 touches
3 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
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
6 conflicts on slot 0xf6650a7492…e644b9
Audit this contract →
← previous block·next block →recent activity