← previous blocknext block →recent activity
Analyzing
Block #91,541,570
20 transactions · 18 stateful · 2026-07-30 05:04:47 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,541,570 · 20 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
4w06w17w08w19w010w111w212w313w314w215w418w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x746bcce3…d0ce
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x2e9d65ac…2265
0x34b655…2a6f
4 touches
1 conflict
0x3055b4d0…81c0
0x34b655…2a6f
4 touches
1 conflict
0x35b0198e…3e0d
0x34b655…2a6f
4 touches
1 conflict
0x38bdc5d3…a632
0x34b655…2a6f
4 touches
1 conflict
0x41891af2…ed2a
0x34b655…2a6f
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 0x746bcce3fa…c7d0ce
Audit this contract →
← previous block·next block →recent activity