← previous blocknext block →recent activity
Analyzing
Block #91,835,152
11 transactions · 8 stateful · 2026-07-31 05:41:37 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,835,152 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60a899fe…e7a2
0x34b655…2a6f
4 touches
1 conflict
0xfd42a6b9…4c81
0x34b655…2a6f
4 touches
1 conflict
0xe413fc94…da2c
0x34b655…2a6f
4 touches
1 conflict
0xdbae25a9…d6f4
0x34b655…2a6f
4 touches
1 conflict
0xcf34dfba…1d81
0x34b655…2a6f
4 touches
1 conflict
0xcf34dfba…1d80
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
1 conflict on slot 0x60a899fedd…82e7a2
Audit this contract →
← previous block·next block →recent activity