← previous blocknext block →recent activity
Analyzing
Block #91,087,572
21 transactions · 17 stateful · 2026-07-28 14:58:29 UTC
Parallelism
90/100
Blocked
18%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,087,572 · 21 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
6w07w110w013w014w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69e18919…f3a5
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0x40970e69…da50
0x2b46c0…1669
2 touches
0 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
2 touches
0 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
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 0x69e1891967…13f3a5
Audit this contract →
← previous block·next block →recent activity