← previous blocknext block →recent activity
Analyzing
Block #91,408,977
13 transactions · 12 stateful · 2026-07-29 17:56:41 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,408,977 · 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
1w02w04w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f8a6b52…6703
0x34b655…2a6f
4 touches
1 conflict
0x45ea7a97…bbb3
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x08024b2c…d265
0x34b655…2a6f
2 touches
0 conflicts
0x0b42fe4a…f5c4
0x34b655…2a6f
2 touches
0 conflicts
0x0b7bd288…2064
0x34b655…2a6f
2 touches
0 conflicts
0x51d03c9d…57a7
0x34b655…2a6f
2 touches
0 conflicts
0x5655f5c3…6b75
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 0x6f8a6b52e0…ba6703
Audit this contract →
← previous block·next block →recent activity