← previous blocknext block →recent activity
Analyzing
Block #90,558,428
16 transactions · 14 stateful · 2026-07-26 18:35:29 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,558,428 · 16 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x699c7f9f…725f
0x34b655…2a6f
4 touches
1 conflict
0x793b6cb1…63c7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x112eb509…62f7
0x34b655…2a6f
2 touches
0 conflicts
0x223f6d48…a374
0x34b655…2a6f
2 touches
0 conflicts
0x223f6d48…a375
0x34b655…2a6f
2 touches
0 conflicts
0x232f95c2…1d16
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 0x699c7f9f4b…e7725f
Audit this contract →
← previous block·next block →recent activity