← previous blocknext block →recent activity
Analyzing
Block #91,409,878
18 transactions · 15 stateful · 2026-07-29 18:01:17 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
0.94
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,409,878 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w19w211w312w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7e1faa73…bfbf
0x34b655…2a6f
8 touches
6 conflicts
0x7ad0d3dc…c4be
0x34b655…2a6f
6 touches
3 conflicts
0x5502e1cc…3910
0x34b655…2a6f
6 touches
3 conflicts
0x747f609d…1555
0x34b655…2a6f
6 touches
3 conflicts
0x353a3a00…5e0a
0x34b655…2a6f
5 touches
3 conflicts
0x8b46e9d1…e148
0x34b655…2a6f
4 touches
1 conflict
0xabf57eb6…416d
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity