← previous blocknext block →recent activity
Analyzing
Block #91,544,798
11 transactions · 11 stateful · 2026-07-30 05:21:02 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.73
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,544,798 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc492e66a…4af0
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x9a7be229…5108
0x34b655…2a6f
6 touches
3 conflicts
0xd6195af4…534d
0x34b655…2a6f
4 touches
1 conflict
0x351d96b9…c5df
0x34b655…2a6f
4 touches
1 conflict
0x94d0ccfd…76d2
0x34b655…2a6f
4 touches
1 conflict
0xb39cb1d8…effa
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 0xc492e66a2e…1d4af0
Audit this contract →
← previous block·next block →recent activity