← previous blocknext block →recent activity
Analyzing
Block #90,614,655
11 transactions · 9 stateful · 2026-07-26 23:18:21 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,614,655 · 11 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
1w02w14w06w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6cfabf20…d256
0x34b655…2a6f
6 touches
3 conflicts
0x0c33bb29…c6a9
0x34b655…2a6f
4 touches
1 conflict
0xed59b1cd…8509
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x99ac26a0…fa05
0x34b655…2a6f
4 touches
1 conflict
0xb5380158…57c4
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xec152baf…a069
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 0x6cfabf2053…bad256
Audit this contract →
← previous block·next block →recent activity