← previous blocknext block →recent activity
Analyzing
Block #90,795,091
21 transactions · 20 stateful · 2026-07-27 14:26:05 UTC
Parallelism
76/100
Blocked
25%
Avg conflicts / tx
0.29
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,795,091 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w111w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24eaf46d…8c2e
0x34b655…2a6f
6 touches
3 conflicts
0x5778d110…d2e6
0xc8689a…ee79
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x55012d1a…3907
0x2b46c0…1669
4 touches
1 conflict
0xdb067026…9eb8
0x2b46c0…1669
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
3 conflicts on slot 0x24eaf46d19…768c2e
Audit this contract →
← previous block·next block →recent activity