← previous blocknext block →recent activity

Analyzing

Block #87,662,146

20 transactions · 16 stateful · 2026-07-14 08:15:53 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,662,146  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x28504822…ded6

0x34b655…2a6f

8 touches
6 conflicts

0xc948dbdc…199a

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x745952b2…d90c

0x34b655…2a6f

6 touches
3 conflicts

0xfde133d7…5e63

0x34b655…2a6f

6 touches
3 conflicts

0x6f761690…95bd

0x34b655…2a6f

4 touches
1 conflict

0xa98e6cb0…8051

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 0x28504822c4…efded6

← previous block·next block →recent activity