← previous blocknext block →recent activity

Analyzing

Block #87,622,751

19 transactions · 18 stateful · 2026-07-14 03:52:36 UTC

Parallelism

79/100

Blocked

33%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,622,751  ·  19 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

0x83b16bf0…4083

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x24879b67…0bdc

0x34b655…2a6f

4 touches
1 conflict

0x44df3c2a…bafe

0x34b655…2a6f

4 touches
1 conflict

0x44df3c2a…baff

0x34b655…2a6f

4 touches
1 conflict

0x5036f376…c06a

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: Perpl

6 conflicts on slot 0x83b16bf09e…e54083

← previous block·next block →recent activity