← previous blocknext block →recent activity
Analyzing
Block #91,834,865
42 transactions · 25 stateful · 2026-07-31 05:40:10 UTC
Parallelism
88/100
Blocked
44%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,834,865 · 42 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
4w06w113w214w316w017w121w022w128w229w332w435w338w039w140w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x9a555477…19a8
0x754704…b603
8 touches
6 conflicts
0x00000000…0004
0x63e48b…53f2
8 touches
6 conflicts
0x00000000…0000
0x63e48b…53f2
8 touches
6 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
8 touches
6 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity