← previous blocknext block →recent activity
Analyzing
Block #90,630,159
23 transactions · 22 stateful · 2026-07-27 00:36:21 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,630,159 · 23 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
7w08w19w210w311w412w513w616w322w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xbb322930…ace5
0x34b655…2a6f
6 touches
3 conflicts
0x15f968a7…905e
0x34b655…2a6f
6 touches
3 conflicts
0xb5a3b1be…8122
0x34b655…2a6f
6 touches
3 conflicts
0x4ccb5334…7c73
0x34b655…2a6f
4 touches
1 conflict
0x648974d7…0ad7
0x34b655…2a6f
4 touches
1 conflict
0x8eb21bd9…aa8b
0x34b655…2a6f
4 touches
1 conflict
0x94e7f277…471b
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity