← previous blocknext block →recent activity
Analyzing
Block #91,570,642
23 transactions · 19 stateful · 2026-07-30 07:31:00 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,570,642 · 23 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
2w03w14w25w08w110w211w212w313w414w116w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3111eaa6…ae08
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x8f63f383…6eda
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
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 0x3111eaa633…9cae08
Audit this contract →
← previous block·next block →recent activity