← previous blocknext block →recent activity
Analyzing
Block #90,809,115
23 transactions · 21 stateful · 2026-07-27 15:36:39 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,809,115 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w19w010w116w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73320e64…b06f
0x34b655…2a6f
6 touches
3 conflicts
0x935a6a34…1a5f
0xd32edf…ff58
5 touches
3 conflicts
0x41377979…0a18
0x34b655…2a6f
4 touches
1 conflict
0x0d488000…3831
0x34b655…2a6f
4 touches
1 conflict
0x6faaf515…90da
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7d0eaae2…60b7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641e
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 0x73320e6460…2db06f
Audit this contract →
← previous block·next block →recent activity