← previous blocknext block →recent activity
Analyzing
Block #90,895,144
39 transactions · 33 stateful · 2026-07-27 22:49:32 UTC
Parallelism
67/100
Blocked
64%
Avg conflicts / tx
1.41
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #90,895,144 · 39 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w18w09w110w211w012w113w214w315w416w520w621w723w224w125w326w227w828w231w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x0d3b978b…5e8e
0x34b655…2a6f
8 touches
6 conflicts
0xf9e23360…8ef7
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x0d2de0f6…e6c6
0x34b655…2a6f
8 touches
6 conflicts
0x89678d1b…463e
0xa6afd3…d132
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc7d08bca…e210
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity