← previous blocknext block →recent activity

Analyzing

Block #87,317,305

12 transactions · 11 stateful · 2026-07-12 17:49:06 UTC

Parallelism

75/100

Blocked

36%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,317,305  ·  12 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

0x1bff683e…7ecb

0x754704…b603

4 touches
1 conflict

0xbc94dfe1…0b3d

0x34b655…2a6f

4 touches
1 conflict

0xbdf1e736…db04

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xc8d31c56…91df

0x34b655…2a6f

4 touches
1 conflict

0xfaef08b1…0696

0x34b655…2a6f

4 touches
1 conflict

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x6278b1b2…ba7b

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 0x1bff683e61…e67ecb

← previous block·next block →recent activity