← previous blocknext block →recent activity

Analyzing

Block #87,643,716

23 transactions · 20 stateful · 2026-07-14 06:12:46 UTC

Parallelism

78/100

Blocked

40%

Avg conflicts / tx

0.74

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,643,716  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xb5a3b1be…8122

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0xd19c9d38…b459

0x34b655…2a6f

6 touches
3 conflicts

0x4f4a7ac3…021c

0x34b655…2a6f

6 touches
3 conflicts

0xc36fa358…24cb

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xd50d8366…df9c

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

10 conflicts on slot 0xb5a3b1be7c…288122

← previous block·next block →recent activity