← previous blocknext block →recent activity
Analyzing
Block #85,100,700
42 transactions · 35 stateful · 2026-07-02 11:11:54 UTC
Parallelism
64/100
Blocked
71%
Avg conflicts / tx
2
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #85,100,700 · 42 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w28w314w015w116w217w318w419w520w621w722w825w227w429w330w331w432w433w540w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
10 touches
10 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
10 touches
10 conflicts
0xc1647db7…f853
0x34b655…2a6f
10 touches
10 conflicts
0xc83310b1…c778
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe47478a3…a058
0x34b655…2a6f
10 touches
10 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
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity