← previous blocknext block →recent activity

Analyzing

Block #87,585,107

24 transactions · 22 stateful · 2026-07-13 23:40:53 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

1.17

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,585,107  ·  24 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

0x7e5ea60a…c4aa

0x34b655…2a6f

12 touches
15 conflicts

0x0733be30…112f

0x34b655…2a6f

10 touches
10 conflicts

0xa562e808…4bde

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

8 touches
6 conflicts

0x8252706a…7ca5

0x34b655…2a6f

6 touches
3 conflicts

0x65b64b8a…13c7

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

15 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity