← previous blocknext block →recent activity
Analyzing
Block #90,787,817
30 transactions · 24 stateful · 2026-07-27 13:49:29 UTC
Parallelism
73/100
Blocked
54%
Avg conflicts / tx
1.03
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,787,817 · 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
3w04w110w011w112w013w114w215w316w417w519w520w221w222w326w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x538f77c2…a9e7
0xa6afd3…d132
6 touches
3 conflicts
0x91803cbc…2f15
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0x9db3090e…7fb8
0x34b655…2a6f
4 touches
1 conflict
0xa84ac543…8b65
0x34b655…2a6f
4 touches
1 conflict
0xb6fdc784…0382
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