← previous blocknext block →recent activity
Analyzing
Block #91,135,674
17 transactions · 17 stateful · 2026-07-28 19:00:29 UTC
Parallelism
59/100
Blocked
53%
Avg conflicts / tx
1.94
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,135,674 · 17 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
1w02w13w24w37w48w410w511w612w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xb56f0740…7542
0x34b655…2a6f
12 touches
15 conflicts
0xc41a18a7…632d
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xf346808d…6ad4
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
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
21 conflicts on slot 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity