← previous blocknext block →recent activity
Analyzing
Block #90,801,967
34 transactions · 21 stateful · 2026-07-27 15:00:41 UTC
Parallelism
88/100
Blocked
48%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,801,967 · 34 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
1w02w14w05w16w07w117w218w019w124w125w029w230w331w032w133w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x405da62e…192a
0xa6afd3…d132
6 touches
3 conflicts
0x731f2745…9370
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe2263bea…6a9e
0x2b46c0…1669
4 touches
1 conflict
0xed7dd7db…6022
0x2b46c0…1669
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