← previous blocknext block →recent activity
Analyzing
Block #91,779,736
24 transactions · 19 stateful · 2026-07-31 01:02:50 UTC
Parallelism
88/100
Blocked
26%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,779,736 · 24 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
2w03w14w27w011w119w221w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c16527f…628c
0x34b655…2a6f
6 touches
3 conflicts
0x4f1ad4b4…e00a
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xb5c4826d…bdd6
0x2b46c0…1669
4 touches
1 conflict
0xb8fccd1b…b5f2
0x2b46c0…1669
4 touches
1 conflict
0xdb067026…9eb8
0x2b46c0…1669
4 touches
1 conflict
0x4d1fe84d…912e
0x34b655…2a6f
4 touches
1 conflict
0x5778d110…d2e6
0xc8689a…ee79
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
3 conflicts on slot 0x5c16527f85…5b628c
Audit this contract →
← previous block·next block →recent activity