← previous blocknext block →recent activity
Analyzing
Block #106,454,054
31 transactions · 24 stateful · 2026-09-20 11:42:17 UTC
Parallelism
84/100
Blocked
46%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,454,054 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w012w113w217w118w121w124w225w226w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4154323…6854
0x34b655…2a6f
8 touches
6 conflicts
0x3a923e2d…4443
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
6 touches
3 conflicts
0x794b8f81…3eaa
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0xa4154323bd…8f6854
Audit this contract →
← previous block·next block →recent activity