← previous blocknext block →recent activity
Analyzing
Block #91,824,338
13 transactions · 12 stateful · 2026-07-31 04:47:12 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,824,338 · 13 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
2w03w15w26w38w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2d7ddf1…388e
0x34b655…2a6f
6 touches
3 conflicts
0x949fc5d9…55f3
0x34b655…2a6f
6 touches
3 conflicts
0xc71887ae…9f3b
0x34b655…2a6f
6 touches
3 conflicts
0xd2d3fe13…b827
0x34b655…2a6f
6 touches
3 conflicts
0xd2d3fe13…b828
0x34b655…2a6f
6 touches
3 conflicts
0x1b5a716b…2302
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6507044e…bcd6
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 0xe2d7ddf128…94388e
Audit this contract →
← previous block·next block →recent activity