← previous blocknext block →recent activity
Analyzing
Block #91,546,597
12 transactions · 10 stateful · 2026-07-30 05:30:04 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,546,597 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd800e635…b1d7
0x34b655…2a6f
4 touches
1 conflict
0x71c4c8cb…7032
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x07cbae0b…e7a2
0x34b655…2a6f
2 touches
0 conflicts
0x4c207091…07e3
0x34b655…2a6f
2 touches
0 conflicts
0x5a79b327…40f9
0x34b655…2a6f
2 touches
0 conflicts
0x65d63aa3…d144
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xd800e635bc…14b1d7
Audit this contract →
← previous block·next block →recent activity