← previous blocknext block →recent activity
Analyzing
Block #90,794,397
35 transactions · 31 stateful · 2026-07-27 14:22:35 UTC
Parallelism
69/100
Blocked
55%
Avg conflicts / tx
1.51
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #90,794,397 · 35 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w18w19w214w015w116w217w318w419w520w621w725w329w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x033cf007…136d
0x34b655…2a6f
8 touches
6 conflicts
0xde9d38a8…4c0f
0x34b655…2a6f
8 touches
6 conflicts
0x0f7df08f…cad4
0xa6afd3…d132
6 touches
3 conflicts
0xb984ae19…d7ef
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity