← previous blocknext block →recent activity
Analyzing
Block #90,784,265
19 transactions · 19 stateful · 2026-07-27 13:31:35 UTC
Parallelism
79/100
Blocked
53%
Avg conflicts / tx
0.84
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,784,265 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w07w18w19w211w213w216w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb31d278…9107
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x17e90565…d957
0xa6afd3…d132
6 touches
3 conflicts
0x561ad161…c172
0xa6afd3…d132
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x06c2c8c1…c2a8
0x34b655…2a6f
4 touches
1 conflict
0x11d87f04…4e45
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
3 conflicts on slot 0xfb31d278a3…299107
Audit this contract →
← previous block·next block →recent activity