← previous blocknext block →recent activity
Analyzing
Block #91,417,185
23 transactions · 16 stateful · 2026-07-29 18:38:06 UTC
Parallelism
74/100
Blocked
38%
Avg conflicts / tx
0.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,417,185 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w012w117w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x9a573905…60cf
0x34b655…2a6f
6 touches
3 conflicts
0x22ce1aa0…6e58
0x34b655…2a6f
4 touches
1 conflict
0x3f85f288…7c97
0x34b655…2a6f
4 touches
1 conflict
0x418f6232…2de6
0x34b655…2a6f
4 touches
1 conflict
0x54836d65…80ab
0x34b655…2a6f
4 touches
1 conflict
0x608214b4…98df
0x34b655…2a6f
4 touches
1 conflict
0x8b46e9d1…e148
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity