← previous blocknext block →recent activity
Analyzing
Block #90,555,922
10 transactions · 9 stateful · 2026-07-26 18:22:53 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,555,922 · 10 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
4w05w16w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf99b312f…ade0
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2c4e81fb…c4c8
0x34b655…2a6f
2 touches
0 conflicts
0x477f51f4…6b59
0x34b655…2a6f
2 touches
0 conflicts
0x59f05e78…e6f9
0x34b655…2a6f
2 touches
0 conflicts
0x630f113e…c9c6
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 0xf99b312f3d…5fade0
Audit this contract →
← previous block·next block →recent activity