← previous blocknext block →recent activity
Analyzing
Block #91,763,905
11 transactions · 7 stateful · 2026-07-30 23:43:12 UTC
Parallelism
64/100
Blocked
57%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,763,905 · 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
4w05w16w28w39w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x8218911e…3bed
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x14002e42…475a
0x34b655…2a6f
2 touches
0 conflicts
0x2ec6a4bc…c7ba
0x34b655…2a6f
2 touches
0 conflicts
0x502b3ee1…7f7b
0x34b655…2a6f
2 touches
0 conflicts
0x502b3ee1…7f7c
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity