← previous blocknext block →recent activity
Analyzing
Block #91,073,558
42 transactions · 35 stateful · 2026-07-28 13:47:55 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
1.48
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #91,073,558 · 42 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w06w17w08w19w210w311w412w513w618w719w821w122w123w825w228w134w835w936w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xda2ee2e7…968a
0x34b655…2a6f
8 touches
6 conflicts
0x7b80de04…86d1
0x34b655…2a6f
8 touches
6 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x80cc3ecc…b09d
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x8fa9bc45…e08f
0xa6afd3…d132
6 touches
3 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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity