← previous blocknext block →recent activity

Analyzing

Block #87,879,428

16 transactions · 15 stateful · 2026-07-15 08:29:29 UTC

Parallelism

56/100

Blocked

60%

Avg conflicts / tx

1.31

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,879,428  ·  16 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x0733be30…112f

0x34b655…2a6f

12 touches
15 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

12 touches
15 conflicts

0x88f37d98…6792

0x34b655…2a6f

8 touches
6 conflicts

0x7139bf32…c881

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4a4

0x34b655…2a6f

8 touches
6 conflicts

0x1061f52b…1c76

0x34b655…2a6f

8 touches
6 conflicts

0x0086c941…5d72

0x34b655…2a6f

8 touches
6 conflicts

0xce75cca8…2fbf

0x34b655…2a6f

8 touches
6 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

15 conflicts on slot 0x0733be30d6…38112f

← previous block·next block →recent activity