← previous blocknext block →recent activity
Analyzing
Block #91,431,965
20 transactions · 19 stateful · 2026-07-29 19:53:21 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,431,965 · 20 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
3w04w16w07w18w213w317w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86ded711…acb2
0x34b655…2a6f
8 touches
6 conflicts
0x5e782d17…5317
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x4d5053d1…3b7d
0x34b655…2a6f
8 touches
6 conflicts
0x4f3a6b4a…3819
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 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 0x86ded711a0…66acb2
Audit this contract →
← previous block·next block →recent activity