← previous blocknext block →recent activity
Analyzing
Block #91,130,959
7 transactions · 7 stateful · 2026-07-28 18:36:46 UTC
Parallelism
57/100
Blocked
29%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,130,959 · 7 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
1w02w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xa779293b…5e59
0x34b655…2a6f
4 touches
1 conflict
0x0672e4a2…8d1f
0x34b655…2a6f
2 touches
0 conflicts
0x1cc2362d…1fb1
0x34b655…2a6f
2 touches
0 conflicts
0x32ffd4e4…5fdd
0x34b655…2a6f
2 touches
0 conflicts
0x35563c03…7689
0x34b655…2a6f
2 touches
0 conflicts
0x3cb7ee74…b8a5
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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity