← previous blocknext block →recent activity
Analyzing
Block #90,772,807
48 transactions · 39 stateful · 2026-07-27 12:33:56 UTC
Parallelism
65/100
Blocked
69%
Avg conflicts / tx
2.13
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #90,772,807 · 48 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w18w09w110w214w016w117w018w119w224w527w628w729w830w131w232w333w337w1143w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x26d1c221…4d2a
0x34b655…2a6f
8 touches
6 conflicts
0x99c5409a…25b7
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x0dfbb457…baaf
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity