← previous blocknext block →recent activity
Analyzing
Block #90,222,700
13 transactions · 13 stateful · 2026-07-25 14:11:36 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,222,700 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cb89fd4…9bb8
0x34b655…2a6f
6 touches
3 conflicts
0xba02be65…f676
0x34b655…2a6f
6 touches
3 conflicts
0x320701d5…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x50e616e2…8782
0x34b655…2a6f
4 touches
1 conflict
0x61e01cd0…b73e
0x34b655…2a6f
4 touches
1 conflict
0x61e01cd0…b73f
0x34b655…2a6f
4 touches
1 conflict
0x64914660…f959
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
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 0x4cb89fd414…2a9bb8
Audit this contract →
← previous block·next block →recent activity