← previous blocknext block →recent activity
Analyzing
Block #90,789,621
20 transactions · 16 stateful · 2026-07-27 13:58:34 UTC
Parallelism
80/100
Blocked
56%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,789,621 · 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
2w03w14w26w07w18w29w311w012w115w318w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xe2263bea…6a9d
0x2b46c0…1669
4 touches
1 conflict
0xe2263bea…6a9e
0x2b46c0…1669
4 touches
1 conflict
0xe2263bea…6a9f
0x2b46c0…1669
4 touches
1 conflict
0xe2263bea…6aa0
0x2b46c0…1669
4 touches
1 conflict
0xea8e47b0…abfe
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: 0x48cba278…e2b48b
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity