← previous blocknext block →recent activity
Analyzing
Block #91,282,903
10 transactions · 9 stateful · 2026-07-29 07:21:59 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,282,903 · 10 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
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c390858…b1ed
0x34b655…2a6f
4 touches
1 conflict
0x41f1e2e5…2edf
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x262d4253…b091
0x34b655…2a6f
2 touches
0 conflicts
0x2c4e81fb…c4c8
0x34b655…2a6f
2 touches
0 conflicts
0x590f63c9…5df9
0x34b655…2a6f
2 touches
0 conflicts
0x59f05e78…e6f9
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 0x2c3908588c…50b1ed
Audit this contract →
← previous block·next block →recent activity