← previous blocknext block →recent activity
Analyzing
Block #90,890,918
18 transactions · 18 stateful · 2026-07-27 22:28:17 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,890,918 · 18 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
2w03w04w16w07w18w29w310w411w212w313w414w517w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x6771eae2…7014
0x34b655…2a6f
10 touches
10 conflicts
0xf79df061…e005
0xe52b14…7230
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xffb2bfcf…b92a
0x34b655…2a6f
8 touches
6 conflicts
0xa93c5a4e…7108
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity