← previous blocknext block →recent activity
Analyzing
Block #91,274,466
12 transactions · 10 stateful · 2026-07-29 06:39:29 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,274,466 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b4ca0c3…fdb4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x152f8e3d…3da0
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2bbc37af…2efe
0x34b655…2a6f
2 touches
0 conflicts
0x2f98c18a…56f8
0x34b655…2a6f
2 touches
0 conflicts
0x421099c9…8896
0x34b655…2a6f
2 touches
0 conflicts
0x446e4f62…f7b6
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x5b4ca0c30d…d3fdb4
Audit this contract →
← previous block·next block →recent activity