← previous blocknext block →recent activity
Analyzing
Block #90,799,923
28 transactions · 22 stateful · 2026-07-27 14:50:24 UTC
Parallelism
86/100
Blocked
41%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,799,923 · 28 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
3w04w15w26w313w014w119w222w323w024w125w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb05cd4f5…73d0
0x2b46c0…1669
8 touches
6 conflicts
0x00000000…004b
0x80c745…7210
8 touches
6 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
8 touches
6 conflicts
0xdb067026…9eb8
0x2b46c0…1669
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x405da62e…192a
0xa6afd3…d132
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xb476ee35…c627
0xa6afd3…d132
8 touches
6 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: 0x2b46c08c…ec1669
6 conflicts on slot 0xb05cd4f5f9…f973d0
Audit this contract →
← previous block·next block →recent activity