← previous blocknext block →recent activity
Analyzing
Block #90,638,248
21 transactions · 20 stateful · 2026-07-27 01:17:03 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,638,248 · 21 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
1w02w13w29w011w012w113w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
12 touches
15 conflicts
0x4bc1abab…5874
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0xf3d10975…0d07
0x34b655…2a6f
12 touches
15 conflicts
0xe4e2ed0a…a2ef
0x34b655…2a6f
9 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xa93f9787…ee33
0x34b655…2a6f
5 touches
3 conflicts
0xf8b2ce22…7ded
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
15 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity