← previous blocknext block →recent activity
Analyzing
Block #91,769,350
21 transactions · 18 stateful · 2026-07-31 00:10:35 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,769,350 · 21 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
3w04w05w17w18w212w313w016w018w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x84d2bf96…1eea
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x91855e…ac7e
4 touches
1 conflict
0x89999c15…fdac
0x34b655…2a6f
4 touches
1 conflict
0x996f08ac…a055
0x34b655…2a6f
4 touches
1 conflict
0x9a8840ee…9b27
0x34b655…2a6f
4 touches
1 conflict
0x9a8af3c2…e4ae
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
6 conflicts on slot 0x84d2bf96bf…cc1eea
Audit this contract →
← previous block·next block →recent activity