← previous blocknext block →recent activity
Analyzing
Block #91,903,321
13 transactions · 13 stateful · 2026-07-31 11:24:39 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,903,321 · 13 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb39cb1d8…effa
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
2 touches
0 conflicts
0x4e65daf1…ed48
0x34b655…2a6f
2 touches
0 conflicts
0x5ddae008…7f79
0x34b655…2a6f
2 touches
0 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
2 touches
0 conflicts
0x6d4c6050…6e3e
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 0xb39cb1d8c6…28effa
Audit this contract →
← previous block·next block →recent activity