← previous blocknext block →recent activity

Analyzing

Block #87,313,610

20 transactions · 18 stateful · 2026-07-12 17:24:23 UTC

Parallelism

80/100

Blocked

39%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,313,610  ·  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

0x94ba9c4a…41d8

0x34b655…2a6f

8 touches
6 conflicts

0x48de9cd5…2f4c

0x34b655…2a6f

8 touches
6 conflicts

0x75ac5fa0…1808

0x34b655…2a6f

8 touches
6 conflicts

0x0a8f8b9c…3046

0x34b655…2a6f

8 touches
6 conflicts

0xe181f491…f4e3

0x34b655…2a6f

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0xfa2527aa…9dd5

0x34b655…2a6f

6 touches
3 conflicts

0xb8e24fcc…4687

0x34b655…2a6f

6 touches
3 conflicts

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 0x94ba9c4a07…0c41d8

← previous block·next block →recent activity