← previous blocknext block →recent activity
Analyzing
Block #90,805,041
19 transactions · 17 stateful · 2026-07-27 15:16:09 UTC
Parallelism
58/100
Blocked
53%
Avg conflicts / tx
1.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,805,041 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w18w513w014w117w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
8 touches
6 conflicts
0x36ccd82a…7be7
0x34b655…2a6f
4 touches
1 conflict
0x38a06385…ed6a
0x34b655…2a6f
4 touches
1 conflict
0x3e2663d3…a620
0x34b655…2a6f
4 touches
1 conflict
0x4334088a…a88c
0x34b655…2a6f
4 touches
1 conflict
0x45ef9175…5ab2
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity