← previous blocknext block →recent activity

Analyzing

Block #87,870,190

25 transactions · 22 stateful · 2026-07-15 07:27:41 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

1.36

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,870,190  ·  25 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x64aaadbf…f9f3

0x34b655…2a6f

14 touches
21 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x0363d65e…06d2

0x34b655…2a6f

6 touches
3 conflicts

0x94bb14fe…8f47

0x34b655…2a6f

6 touches
3 conflicts

0xbc94dfe1…0b3d

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

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

21 conflicts on slot 0x64aaadbf0a…79f9f3

← previous block·next block →recent activity