← previous blocknext block →recent activity
Analyzing
Block #91,024,977
8 transactions · 8 stateful · 2026-07-28 09:43:31 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,024,977 · 8 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5df7cf2b…bbe5
0x34b655…2a6f
4 touches
1 conflict
0x3aac0597…8e4a
0x34b655…2a6f
4 touches
1 conflict
0x312c6e56…3d7a
0x34b655…2a6f
4 touches
1 conflict
0xe26aee7b…f52b
0x34b655…2a6f
4 touches
1 conflict
0xe5eb3c33…0e3a
0x34b655…2a6f
4 touches
1 conflict
0xe8eae8a3…bacc
0x34b655…2a6f
4 touches
1 conflict
0x1761c637…ed10
0x34b655…2a6f
2 touches
0 conflicts
0x3f2796bf…f0fa
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 0x5df7cf2bfe…17bbe5
Audit this contract →
← previous block·next block →recent activity