← previous blocknext block →recent activity
Analyzing
Block #90,797,264
60 transactions · 51 stateful · 2026-07-27 14:37:01 UTC
Parallelism
75/100
Blocked
57%
Avg conflicts / tx
1.78
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #90,797,264 · 60 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w17w08w010w113w314w116w017w118w219w321w022w123w224w325w426w527w628w729w833w250w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0x00000000…00c9
0x34b655…2a6f
12 touches
15 conflicts
0x58d6b9cf…7c9e
0x34b655…2a6f
10 touches
10 conflicts
0x53f393fa…00b9
0x34b655…2a6f
10 touches
10 conflicts
0x9538ea90…0536
0x34b655…2a6f
8 touches
6 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x9fd372a1…a959
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
45 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity