← previous blocknext block →recent activity
Analyzing
Block #90,991,692
12 transactions · 12 stateful · 2026-07-28 06:55:18 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,991,692 · 12 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w47w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x87328177…9bfd
0x34b655…2a6f
6 touches
3 conflicts
0x1175233a…64e7
0x34b655…2a6f
4 touches
1 conflict
0x2dd83168…8144
0x34b655…2a6f
4 touches
1 conflict
0x363f99e4…32c8
0x34b655…2a6f
4 touches
1 conflict
0x39e478e5…5f31
0x34b655…2a6f
4 touches
1 conflict
0x3ca268be…8865
0x34b655…2a6f
4 touches
1 conflict
0x53a7111b…8897
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity