← previous blocknext block →recent activity

Analyzing

Block #86,366,341

20 transactions · 17 stateful · 2026-07-08 07:50:17 UTC

Parallelism

80/100

Blocked

41%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,366,341  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x2d04e49f…3323

0x34b655…2a6f

4 touches
1 conflict

0x5970f8ee…184d

0x34b655…2a6f

4 touches
1 conflict

0x7a2fc410…c088

0x34b655…2a6f

4 touches
1 conflict

0xa2dd7133…24d0

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