← previous blocknext block →recent activity
Analyzing
Block #91,131,074
14 transactions · 14 stateful · 2026-07-28 18:37:21 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,131,074 · 14 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
1w02w13w24w38w49w510w612w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42578f4c…5779
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xbaec1954…dca5
0x34b655…2a6f
6 touches
3 conflicts
0xbc66586e…20fe
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
6 touches
3 conflicts
0xebac0f82…a49c
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 0x42578f4cad…095779
Audit this contract →
← previous block·next block →recent activity