← previous blocknext block →recent activity

Analyzing

Block #86,844,831

15 transactions · 12 stateful · 2026-07-10 13:10:30 UTC

Parallelism

73/100

Blocked

33%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,844,831  ·  15 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x42041fec…bd86

0x754704…b603

8 touches
6 conflicts

0x26c60bc6…bfe3

0x34b655…2a6f

4 touches
1 conflict

0x1a7886fb…b733

0x34b655…2a6f

4 touches
1 conflict

0x367b69ad…33d8

0x34b655…2a6f

4 touches
1 conflict

0x367b69ad…33d9

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7babfe9a…ff96

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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: USDC (USDC)

6 conflicts on slot 0x42041feca2…afbd86

← previous block·next block →recent activity