← previous blocknext block →recent activity
Analyzing
Block #90,794,093
46 transactions · 35 stateful · 2026-07-27 14:21:04 UTC
Parallelism
89/100
Blocked
49%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,794,093 · 46 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
1w04w05w16w17w09w110w220w021w122w224w325w029w130w031w132w133w234w436w237w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…004b
0x80c745…7210
8 touches
6 conflicts
0x00000000…004c
0x80c745…7210
8 touches
6 conflicts
0x0f7df08f…cad4
0xa6afd3…d132
6 touches
3 conflicts
0x22e0cc1d…ad04
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity