← previous blocknext block →recent activity

Analyzing

Block #87,589,491

25 transactions · 19 stateful · 2026-07-14 00:10:12 UTC

Parallelism

64/100

Blocked

47%

Avg conflicts / tx

0.92

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,589,491  ·  25 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

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0004

0x158622…375e

8 touches
6 conflicts

0x52f7c71c…d0a6

0x34b655…2a6f

6 touches
3 conflicts

0x7527802e…2ba9

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1af

0x158622…375e

4 touches
4 conflicts

0x4a467902…004e

0x34b655…2a6f

4 touches
1 conflict

0x5a19ef35…dc70

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

10 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity