← previous blocknext block →recent activity
Analyzing
Block #91,109,365
11 transactions · 10 stateful · 2026-07-28 16:48:09 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,109,365 · 11 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
2w07w18w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc58c80b…ff79
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc0dfa1c0…e6af
0x34b655…2a6f
6 touches
3 conflicts
0x84d74093…7808
0x34b655…2a6f
6 touches
3 conflicts
0xa1501442…6ac0
0x34b655…2a6f
6 touches
3 conflicts
0x6d94ea59…6891
0x34b655…2a6f
4 touches
1 conflict
0xa9fa41ff…ae71
0x34b655…2a6f
4 touches
1 conflict
0x9e1423e0…9c81
0x34b655…2a6f
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
3 conflicts on slot 0xcc58c80b6c…80ff79
Audit this contract →
← previous block·next block →recent activity