← previous blocknext block →recent activity
Analyzing
Block #91,189,963
17 transactions · 17 stateful · 2026-07-28 23:33:36 UTC
Parallelism
59/100
Blocked
65%
Avg conflicts / tx
1.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,189,963 · 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
1w02w03w14w25w36w38w49w510w612w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x91ac91ec…eea0
0x34b655…2a6f
8 touches
6 conflicts
0x391d75c5…b826
0x34b655…2a6f
7 touches
6 conflicts
0xa45116ed…5331
0x34b655…2a6f
6 touches
3 conflicts
0x705ab4ae…0162
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity