← previous blocknext block →recent activity

Analyzing

Block #87,918,587

23 transactions · 19 stateful · 2026-07-15 12:51:24 UTC

Parallelism

87/100

Blocked

37%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,918,587  ·  23 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x6f7775d0…a8b4

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xe718f3c7…c376

0x34b655…2a6f

6 touches
3 conflicts

0x263aa68b…6c6a

0x34b655…2a6f

4 touches
1 conflict

0x274ac476…27fa

0x34b655…2a6f

4 touches
1 conflict

0x53a34840…b621

0x34b655…2a6f

4 touches
1 conflict

0x5a124748…29a7

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

3 conflicts on slot 0x6f7775d097…62a8b4

← previous block·next block →recent activity