← previous blocknext block →recent activity

Analyzing

Block #87,133,392

14 transactions · 13 stateful · 2026-07-11 21:18:38 UTC

Parallelism

86/100

Blocked

31%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #87,133,392  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xad676684…c58b

0x754704…b603

4 touches
1 conflict

0x0a906ba5…2454

0x34b655…2a6f

4 touches
1 conflict

0x21082490…de66

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x6719a767…9d62

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x953517cb…cdec

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)

1 conflict on slot 0xad6766848e…91c58b

← previous block·next block →recent activity