← previous blocknext block →recent activity
Analyzing
Block #91,001,668
13 transactions · 12 stateful · 2026-07-28 07:45:54 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,001,668 · 13 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
6w07w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c7f2108…99fd
0x34b655…2a6f
4 touches
1 conflict
0x808aff35…5c6f
0x34b655…2a6f
4 touches
1 conflict
0x95dd1dda…bc0e
0x34b655…2a6f
4 touches
1 conflict
0x7133f06a…742a
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0bfc83e5…e8eb
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
1 conflict on slot 0x2c7f21086d…6899fd
Audit this contract →
← previous block·next block →recent activity