← previous blocknext block →recent activity

Analyzing

Block #87,583,062

25 transactions · 20 stateful · 2026-07-13 23:27:13 UTC

Parallelism

72/100

Blocked

45%

Avg conflicts / tx

0.92

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,583,062  ·  25 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

0x207b4a17…4084

0x34b655…2a6f

8 touches
6 conflicts

0x7b2f3e6d…978f

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0xd6a90a81…3b3d

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x8252706a…7ca5

0x34b655…2a6f

6 touches
3 conflicts

0x4c990b3a…9900

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

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 0x207b4a17c3…494084

← previous block·next block →recent activity