← previous blocknext block →recent activity
Analyzing
Block #91,077,056
20 transactions · 20 stateful · 2026-07-28 14:05:33 UTC
Parallelism
80/100
Blocked
45%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,077,056 · 20 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
1w02w03w14w25w06w18w09w111w114w115w218w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4e0a934…5fc7
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xeb45cf15…e0a6
0x065c9d…c394
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0aa283ae…ef9c
0x34b655…2a6f
4 touches
1 conflict
0x11f2aded…153a
0x34b655…2a6f
4 touches
1 conflict
0x19c5bd01…7daf
0x34b655…2a6f
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
3 conflicts on slot 0xb4e0a934b9…435fc7
Audit this contract →
← previous block·next block →recent activity