← previous blocknext block →recent activity
Analyzing
Block #90,851,949
20 transactions · 19 stateful · 2026-07-27 19:12:12 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,851,949 · 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
1w02w13w05w06w18w210w312w413w515w216w617w119w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b1ce1dd…dc2f
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xde9d38a8…4c0f
0x34b655…2a6f
8 touches
6 conflicts
0x4f893478…c649
0x34b655…2a6f
8 touches
6 conflicts
0xed1bb940…3dcb
0x34b655…2a6f
6 touches
3 conflicts
0x358d6b84…2f88
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd459bf7b…92c3
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
10 conflicts on slot 0x3b1ce1dd02…5adc2f
Audit this contract →
← previous block·next block →recent activity