← previous blocknext block →recent activity
Analyzing
Block #90,770,910
20 transactions · 19 stateful · 2026-07-27 12:24:24 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,770,910 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w18w19w210w011w112w215w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde9d38a8…4c0f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x006c3b86…59a9
0x34b655…2a6f
4 touches
1 conflict
0x358d6b84…2f88
0x34b655…2a6f
4 touches
1 conflict
0x3b1ce1dd…dc2f
0x34b655…2a6f
4 touches
1 conflict
0x526dcf24…1100
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
10 conflicts on slot 0xde9d38a88f…994c0f
Audit this contract →
← previous block·next block →recent activity