← previous blocknext block →recent activity
Analyzing
Block #90,524,333
10 transactions · 10 stateful · 2026-07-26 15:44:00 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,524,333 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe00608f8…edc2
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x241be30a…4b67
0x0c65a0…0852
2 touches
0 conflicts
0xaf41644f…8f2e
0x0c65a0…0852
2 touches
0 conflicts
0x6676e87f…b88f
0x2a68ba…90c5
2 touches
0 conflicts
0xdaf4f143…58d4
0x2a68ba…90c5
2 touches
0 conflicts
0x3d4c0233…20a5
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xe00608f80d…a6edc2
Audit this contract →
← previous block·next block →recent activity