← previous blocknext block →recent activity
Analyzing
Block #90,644,850
17 transactions · 17 stateful · 2026-07-27 01:50:15 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,644,850 · 17 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
1w02w13w24w15w06w17w08w29w310w111w013w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb8dc535…4fe7
0x34b655…2a6f
6 touches
3 conflicts
0x7789d7be…ad2d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x02f33538…e32b
0xd32edf…ff58
5 touches
3 conflicts
0x275cf790…7288
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xa2e86105…e08c
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0xbb8dc53554…834fe7
Audit this contract →
← previous block·next block →recent activity