← previous blocknext block →recent activity
Analyzing
Block #91,778,727
20 transactions · 16 stateful · 2026-07-31 00:57:46 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,778,727 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w19w012w114w215w317w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4f9cac7…fd98
0x34b655…2a6f
4 touches
1 conflict
0x439cfb2c…7b9e
0xa6afd3…d132
4 touches
1 conflict
0x103be197…826c
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00328012…50b5
0x34b655…2a6f
4 touches
1 conflict
0x124a2fe8…2ea9
0x34b655…2a6f
4 touches
1 conflict
0x17935a8f…a796
0x34b655…2a6f
4 touches
1 conflict
0x1bf8d2af…d140
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 0xf4f9cac7d9…09fd98
Audit this contract →
← previous block·next block →recent activity