← previous blocknext block →recent activity
Analyzing
Block #90,849,580
20 transactions · 17 stateful · 2026-07-27 19:00:17 UTC
Parallelism
75/100
Blocked
41%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,849,580 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w111w212w313w415w016w118w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b224785…8e8c
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x0fffa5c0…a3a9
0xa6afd3…d132
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xcdc1731c…b91a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe4af4c87…9964
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 0x6b2247853d…e58e8c
Audit this contract →
← previous block·next block →recent activity