← previous blocknext block →recent activity
Analyzing
Block #91,980,986
14 transactions · 13 stateful · 2026-07-31 17:55:18 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,980,986 · 14 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
1w02w14w15w28w09w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd693ff4…5072
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x6e6a8155…9636
0x34b655…2a6f
4 touches
1 conflict
0x745a7fd6…5fea
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0xa7e5fdca…4df9
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
6 conflicts on slot 0xbd693ff455…1e5072
Audit this contract →
← previous block·next block →recent activity