← previous blocknext block →recent activity
Analyzing
Block #90,689,040
18 transactions · 17 stateful · 2026-07-27 05:32:34 UTC
Parallelism
72/100
Blocked
53%
Avg conflicts / tx
1.22
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,689,040 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w08w19w110w211w212w313w315w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95c47f03…f1bb
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x561ad161…c172
0xa6afd3…d132
8 touches
6 conflicts
0x83f3d320…fb59
0x34b655…2a6f
6 touches
3 conflicts
0x6e27bdfb…108a
0x34b655…2a6f
6 touches
3 conflicts
0xde945aa8…1ad5
0xa6afd3…d132
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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
10 conflicts on slot 0x95c47f0322…51f1bb
Audit this contract →
← previous block·next block →recent activity