← previous blocknext block →recent activity

Analyzing

Block #87,749,194

18 transactions · 17 stateful · 2026-07-14 17:58:23 UTC

Parallelism

78/100

Blocked

41%

Avg conflicts / tx

0.94

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,749,194  ·  18 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

0xf3d10975…0d07

0x34b655…2a6f

8 touches
6 conflicts

0xc948dbdc…199a

0x34b655…2a6f

8 touches
6 conflicts

0x55c2c22c…0474

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x46a7d766…9797

0x34b655…2a6f

6 touches
3 conflicts

0x35d95fb0…db9e

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x9a2de05d…3e6b

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 0xf3d10975b0…050d07

← previous block·next block →recent activity