← previous blocknext block →recent activity

Analyzing

Block #86,165,919

20 transactions · 20 stateful · 2026-07-07 09:32:05 UTC

Parallelism

90/100

Blocked

30%

Avg conflicts / tx

0.3

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,165,919  ·  20 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

0x4039b31f…0f4a

0x754704…b603

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x456f4453…91f0

0x34b655…2a6f

4 touches
1 conflict

0xb245fe36…d765

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xec0e0220…cb90

0x34b655…2a6f

4 touches
1 conflict

0x5d82c9b5…004c

0x3bd359…433a

4 touches
1 conflict

0x00000000…0004

0x5afd3e…7620

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 0x4039b31fcf…cb0f4a

← previous block·next block →recent activity