← previous blocknext block →recent activity
Analyzing
Block #90,699,684
20 transactions · 19 stateful · 2026-07-27 06:26:07 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,699,684 · 20 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
1w02w13w26w07w18w29w310w414w015w117w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x110a671c…e284
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xd1ec9623…d1d4
0xd32edf…ff58
5 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x821f0b86…7ebb
0x34b655…2a6f
4 touches
1 conflict
0x93b6fab0…09d6
0x34b655…2a6f
4 touches
1 conflict
0xc3e19352…2faf
0x34b655…2a6f
4 touches
1 conflict
0xe4b8f2c5…f54d
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 0x110a671c45…0be284
Audit this contract →
← previous block·next block →recent activity