← previous blocknext block →recent activity
Analyzing
Block #91,019,317
14 transactions · 13 stateful · 2026-07-28 09:15:01 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,019,317 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w09w113w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xc014bcf3…3ac7
0x34b655…2a6f
4 touches
1 conflict
0x442e26a3…e968
0x34b655…2a6f
4 touches
1 conflict
0xe3e6c02a…d3d4
0x34b655…2a6f
4 touches
1 conflict
0x080ca4e8…d573
0x34b655…2a6f
2 touches
0 conflicts
0x0db2eb69…b5e7
0x34b655…2a6f
2 touches
0 conflicts
0x1e4cddcd…a8ca
0x34b655…2a6f
2 touches
0 conflicts
0x21d22421…0b7a
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity