← previous blocknext block →recent activity
Analyzing
Block #91,972,664
24 transactions · 21 stateful · 2026-07-31 17:13:26 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,972,664 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w29w313w014w115w316w419w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x31616f97…1acc
0x34b655…2a6f
8 touches
6 conflicts
0xa8c30853…b2f5
0x7b9256…1fb2
4 touches
1 conflict
0x28931d3a…8306
0x34b655…2a6f
4 touches
1 conflict
0x0f62bc79…1afe
0x7b9256…1fb2
4 touches
1 conflict
0x0f62bc79…1aff
0x7b9256…1fb2
4 touches
1 conflict
0x0f62bc79…1b02
0x7b9256…1fb2
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity