← previous blocknext block →recent activity
Analyzing
Block #91,972,069
31 transactions · 25 stateful · 2026-07-31 17:10:26 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,972,069 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w010w112w213w315w019w020w421w122w223w226w127w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x6e6b8ec7…2197
0x34b655…2a6f
6 touches
3 conflicts
0x02991b41…19e6
0x34b655…2a6f
4 touches
1 conflict
0x0a3b1855…e661
0x34b655…2a6f
4 touches
1 conflict
0x0f6aef87…8137
0x34b655…2a6f
4 touches
1 conflict
0xfa551be3…a911
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity