← previous blocknext block →recent activity
Analyzing
Block #91,128,632
24 transactions · 23 stateful · 2026-07-28 18:25:04 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,128,632 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w27w09w111w314w415w517w621w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc66586e…20fe
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x43e3decb…be40
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
6 touches
3 conflicts
0xa6d7ba81…4ade
0x34b655…2a6f
6 touches
3 conflicts
0x291ac025…6f81
0x34b655…2a6f
5 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
10 conflicts on slot 0xbc66586e8f…a220fe
Audit this contract →
← previous block·next block →recent activity