← previous blocknext block →recent activity

Analyzing

Block #87,624,442

25 transactions · 23 stateful · 2026-07-14 04:03:55 UTC

Parallelism

76/100

Blocked

30%

Avg conflicts / tx

0.68

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,624,442  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x32dfa6a9…12f6

0x34b655…2a6f

8 touches
6 conflicts

0x7527802e…2ba9

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x18904470…0ef9

0x34b655…2a6f

6 touches
3 conflicts

0xd5fbd629…3b7f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x254b4113…6fd2

0x34b655…2a6f

4 touches
1 conflict

0x2b5101ac…090b

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

6 conflicts on slot 0x32dfa6a9da…8f12f6

← previous block·next block →recent activity