← previous blocknext block →recent activity
Analyzing
Block #91,763,395
23 transactions · 22 stateful · 2026-07-30 23:40:38 UTC
Parallelism
74/100
Blocked
36%
Avg conflicts / tx
0.91
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,763,395 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w07w18w09w110w211w212w313w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x7d0eaae2…60b7
0x34b655…2a6f
10 touches
10 conflicts
0x29265bf3…16ba
0x34b655…2a6f
9 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf3383813…4a0c
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x9cf9008a…d826
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
10 conflicts on slot 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity