← previous blocknext block →recent activity
Analyzing
Block #90,960,660
24 transactions · 22 stateful · 2026-07-28 04:19:05 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,960,660 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w17w210w114w215w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x6e6b8ec7…2197
0x34b655…2a6f
8 touches
6 conflicts
0xfddb964d…5934
0x34b655…2a6f
6 touches
3 conflicts
0x98459f89…575d
0x34b655…2a6f
4 touches
1 conflict
0x9a287655…f785
0x34b655…2a6f
4 touches
1 conflict
0x9b2511ba…3812
0x34b655…2a6f
4 touches
1 conflict
0xa6b31cd7…197f
0x34b655…2a6f
4 touches
1 conflict
0xac53dc63…c806
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity