← previous blocknext block →recent activity
Analyzing
Block #91,834,530
15 transactions · 14 stateful · 2026-07-31 05:38:29 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,834,530 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w27w38w412w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2477d0da…f68e
0x34b655…2a6f
6 touches
3 conflicts
0xe670c2b4…f61e
0x34b655…2a6f
6 touches
3 conflicts
0x38c6ff01…689f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x7462b8f2…6312
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd79c9727…1233
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 0x2477d0da59…e4f68e
Audit this contract →
← previous block·next block →recent activity