← previous blocknext block →recent activity
Analyzing
Block #91,768,171
10 transactions · 9 stateful · 2026-07-31 00:04:39 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,768,171 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6fcbbb7…2b31
0x34b655…2a6f
4 touches
1 conflict
0x1cc683f9…4564
0x34b655…2a6f
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
0x0f00f2df…7579
0x34b655…2a6f
2 touches
0 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
2 touches
0 conflicts
0x135a49be…c962
0x34b655…2a6f
2 touches
0 conflicts
0x15b85601…7f03
0x34b655…2a6f
2 touches
0 conflicts
0x1e0cc837…c2b1
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xb6fcbbb7f3…142b31
Audit this contract →
← previous block·next block →recent activity