← previous blocknext block →recent activity
Analyzing
Block #90,840,339
15 transactions · 15 stateful · 2026-07-27 18:13:49 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,840,339 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w17w212w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x663ab2c3…67ab
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0bd95eb4…e562
0x34b655…2a6f
4 touches
1 conflict
0x1a34e47d…b58e
0x34b655…2a6f
4 touches
1 conflict
0x22f59c1f…c61d
0x34b655…2a6f
4 touches
1 conflict
0x3b6e959d…158f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0x663ab2c30e…e367ab
Audit this contract →
← previous block·next block →recent activity