← previous blocknext block →recent activity

Analyzing

Block #87,879,216

22 transactions · 20 stateful · 2026-07-15 08:28:04 UTC

Parallelism

59/100

Blocked

50%

Avg conflicts / tx

1.09

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,879,216  ·  22 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x64a058c6…74a1

0x34b655…2a6f

6 touches
3 conflicts

0x4681609f…6493

0x34b655…2a6f

4 touches
1 conflict

0x48b13e5e…3c2a

0x34b655…2a6f

4 touches
1 conflict

0x5577d7f1…3fb3

0x34b655…2a6f

4 touches
1 conflict

0x64aaadbf…f9f3

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity