← previous blocknext block →recent activity
Analyzing
Block #90,796,058
42 transactions · 32 stateful · 2026-07-27 14:30:57 UTC
Parallelism
74/100
Blocked
66%
Avg conflicts / tx
1.4
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #90,796,058 · 42 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
3w04w05w17w28w317w018w119w220w321w423w524w126w428w629w130w531w233w635w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xb476ee35…c627
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x405da62e…192a
0xa6afd3…d132
8 touches
6 conflicts
0x206f4379…e08a
0x34b655…2a6f
6 touches
3 conflicts
0x2f358e74…1022
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity