← previous blocknext block →recent activity
Analyzing
Block #90,795,541
30 transactions · 24 stateful · 2026-07-27 14:28:21 UTC
Parallelism
73/100
Blocked
46%
Avg conflicts / tx
1.03
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,795,541 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w010w111w212w313w414w517w520w324w625w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x033cf007…136d
0x34b655…2a6f
8 touches
6 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
8 touches
6 conflicts
0x171ff85b…255e
0x34b655…2a6f
4 touches
1 conflict
0x19cbeea8…ecf3
0x34b655…2a6f
4 touches
1 conflict
0x1a5d321d…a474
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x3782a203…e472
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity