← previous blocknext block →recent activity
Analyzing
Block #90,813,888
19 transactions · 19 stateful · 2026-07-27 16:00:45 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.53
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,813,888 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w27w38w310w211w312w413w514w617w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0x4bc1abab…5874
0x34b655…2a6f
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 conflicts
0xbde524f4…43bf
0x34b655…2a6f
10 touches
10 conflicts
0x6bdb9869…7558
0x34b655…2a6f
10 touches
10 conflicts
0x44825bf9…bf85
0x34b655…2a6f
7 touches
6 conflicts
0x731dfd88…9255
0x34b655…2a6f
6 touches
3 conflicts
0x6a764ba5…54b7
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity