← previous blocknext block →recent activity
Analyzing
Block #91,243,407
22 transactions · 20 stateful · 2026-07-29 04:02:25 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
1.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,243,407 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w06w17w210w212w313w414w518w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xfd8783dc…3725
0x34b655…2a6f
6 touches
3 conflicts
0x3b689fd2…629c
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x625d8877…be39
0x34b655…2a6f
6 touches
3 conflicts
0x081eb1d8…4caf
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity