← previous blocknext block →recent activity
Analyzing
Block #91,439,575
16 transactions · 14 stateful · 2026-07-29 20:31:38 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.88
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,439,575 · 16 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
2w03w04w05w06w17w28w19w110w212w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda2ee2e7…968a
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
6 touches
3 conflicts
0x839a9c2c…9b68
0x34b655…2a6f
6 touches
3 conflicts
0x8ffa3328…ce11
0xe52b14…7230
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0x17bbe4f8…08c5
0xe52b14…7230
4 touches
1 conflict
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 0xda2ee2e777…e7968a
Audit this contract →
← previous block·next block →recent activity