← previous blocknext block →recent activity
Analyzing
Block #91,769,088
10 transactions · 10 stateful · 2026-07-31 00:09:16 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,769,088 · 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fe7e126…6dd2
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x02b62ce6…d449
0x34b655…2a6f
2 touches
0 conflicts
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x09a168cc…dcc0
0x34b655…2a6f
2 touches
0 conflicts
0x0d759c8b…b9b2
0x34b655…2a6f
2 touches
0 conflicts
0x26bcd08c…8b42
0x34b655…2a6f
2 touches
0 conflicts
0x2b7e35f7…ff26
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 0x5fe7e1267e…896dd2
Audit this contract →
← previous block·next block →recent activity