← previous blocknext block →recent activity
Analyzing
Block #91,772,164
21 transactions · 19 stateful · 2026-07-31 00:24:44 UTC
Parallelism
86/100
Blocked
37%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,772,164 · 21 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
1w06w08w19w010w211w112w114w015w117w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0xc702abd0…d0b1
0xa6afd3…d132
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xf4f9cac7…fd98
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
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: 0x80c74517…647210
3 conflicts on slot 0x0000000000…00004b
Audit this contract →
← previous block·next block →recent activity