← previous blocknext block →recent activity
Analyzing
Block #90,916,247
15 transactions · 14 stateful · 2026-07-28 00:35:43 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,916,247 · 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
1w04w06w17w08w29w110w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x466c9e6a…e9de
0x34b655…2a6f
6 touches
3 conflicts
0xafb8e71e…9285
0x34b655…2a6f
6 touches
3 conflicts
0xc782ec05…5bb2
0xa6afd3…d132
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x972e38eb…dc76
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x466c9e6a9e…88e9de
Audit this contract →
← previous block·next block →recent activity