← previous blocknext block →recent activity
Analyzing
Block #90,796,848
20 transactions · 19 stateful · 2026-07-27 14:34:55 UTC
Parallelism
70/100
Blocked
37%
Avg conflicts / tx
0.55
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,796,848 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w29w010w311w114w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1c3295fd…097a
0x34b655…2a6f
4 touches
1 conflict
0x22c64700…84b1
0x34b655…2a6f
4 touches
1 conflict
0x64f577fd…e525
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x70b7b52e…7743
0x34b655…2a6f
4 touches
1 conflict
0x757057f2…8eed
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
6 conflicts on slot 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity