← previous blocknext block →recent activity
Analyzing
Block #90,786,940
23 transactions · 22 stateful · 2026-07-27 13:45:03 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
0.83
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,786,940 · 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
1w02w13w24w36w07w18w09w110w211w313w315w418w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
6 touches
3 conflicts
0x40970e69…da50
0x2b46c0…1669
6 touches
3 conflicts
0xb5c4826d…bdd6
0x2b46c0…1669
6 touches
3 conflicts
0xb8fccd1b…b5f2
0x2b46c0…1669
6 touches
3 conflicts
0xdb067026…9eb8
0x2b46c0…1669
6 touches
3 conflicts
0x5778d110…d2e6
0xc8689a…ee79
6 touches
3 conflicts
0x92385428…6941
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity