← previous blocknext block →recent activity

Analyzing

Block #87,611,403

18 transactions · 15 stateful · 2026-07-14 02:36:44 UTC

Parallelism

78/100

Blocked

53%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,611,403  ·  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

0xd64c1971…1bf2

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x0ee13be7…7b2c

0x34b655…2a6f

4 touches
1 conflict

0x17fff7d7…7b99

0x34b655…2a6f

4 touches
1 conflict

0x2b5101ac…090b

0x34b655…2a6f

4 touches
1 conflict

0x4ec199d4…e9f1

0x34b655…2a6f

4 touches
1 conflict

0x4ef82148…8a23

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 0xd64c197151…2d1bf2

← previous block·next block →recent activity