← previous blocknext block →recent activity
Analyzing
Block #90,796,315
22 transactions · 20 stateful · 2026-07-27 14:32:15 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
1.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,796,315 · 22 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
1w05w06w17w28w39w410w511w612w719w521w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x1a5d321d…a474
0x34b655…2a6f
6 touches
3 conflicts
0xe03bbbf2…f240
0x34b655…2a6f
6 touches
3 conflicts
0x1b8a880a…5ce4
0x34b655…2a6f
6 touches
3 conflicts
0xeef479fa…fbf4
0x34b655…2a6f
6 touches
3 conflicts
0x9fd372a1…a959
0x34b655…2a6f
6 touches
3 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
6 touches
3 conflicts
0x483f2f15…8214
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity