← previous blocknext block →recent activity

Analyzing

Block #86,783,029

18 transactions · 16 stateful · 2026-07-10 06:17:19 UTC

Parallelism

83/100

Blocked

44%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,783,029  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xbcc2ea3e…8ea3

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0xc3cda232…10dd

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea297ef6…552d

0x34b655…2a6f

4 touches
1 conflict

0xea297ef6…552e

0x34b655…2a6f

4 touches
1 conflict

0xf2f4727d…cdb7

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)

3 conflicts on slot 0x42041feca2…afbd86

← previous block·next block →recent activity