← previous blocknext block →recent activity
Analyzing
Block #85,131,540
33 transactions · 30 stateful · 2026-07-02 14:38:28 UTC
Parallelism
82/100
Blocked
67%
Avg conflicts / tx
1.55
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,131,540 · 33 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w17w28w39w010w111w213w314w423w224w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0x04fdea…47d7
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x3c7520fc…9ca3
0x34b655…2a6f
8 touches
6 conflicts
0x0f94ee4c…1898
0x1b6862…e19c
6 touches
3 conflicts
0x2406ccf7…c1cb
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity