← previous blocknext block →recent activity
Analyzing
Block #91,832,087
11 transactions · 11 stateful · 2026-07-31 05:26:12 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,832,087 · 11 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
1w02w13w25w38w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f058af7…9d8f
0x34b655…2a6f
6 touches
3 conflicts
0x2fd12b6c…02cc
0x34b655…2a6f
4 touches
1 conflict
0xa0c570a0…7148
0x34b655…2a6f
4 touches
1 conflict
0x3cf9e32f…0f64
0x34b655…2a6f
4 touches
1 conflict
0xb1b58b33…874f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc3baa205…f26e
0x34b655…2a6f
4 touches
1 conflict
0x2b4f3000…10fe
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 0x2f058af77e…f49d8f
Audit this contract →
← previous block·next block →recent activity