← previous blocknext block →recent activity
Analyzing
Block #91,569,205
20 transactions · 18 stateful · 2026-07-30 07:23:47 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,569,205 · 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
1w03w14w27w18w216w317w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1b58b33…874f
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0xace13ee0…a22d
0x34b655…2a6f
4 touches
1 conflict
0xece6a1eb…39fa
0x34b655…2a6f
4 touches
1 conflict
0x3a9e59a0…6198
0x34b655…2a6f
2 touches
0 conflicts
0x420c9f5d…01e9
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 0xb1b58b3385…e4874f
Audit this contract →
← previous block·next block →recent activity