← previous blocknext block →recent activity
Analyzing
Block #85,143,510
26 transactions · 22 stateful · 2026-07-02 15:58:21 UTC
Parallelism
73/100
Blocked
41%
Avg conflicts / tx
0.62
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,143,510 · 26 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
1w02w13w25w28w09w110w211w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xb04d17a0…10e8
0x34b655…2a6f
6 touches
3 conflicts
0x4039b31f…0f4a
0x754704…b603
6 touches
3 conflicts
0x00000000…0004
0x5afd3e…7620
6 touches
3 conflicts
0x5d82c9b5…004c
0x3bd359…433a
6 touches
3 conflicts
0xe237b862…0a91
0xd32edf…ff58
5 touches
3 conflicts
0xba5743c7…21c0
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity