← previous blocknext block →recent activity

Analyzing

Block #87,910,320

23 transactions · 19 stateful · 2026-07-15 11:56:08 UTC

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

0.57

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,910,320  ·  23 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

0x0f6666e6…f280

0x34b655…2a6f

6 touches
3 conflicts

0x5dc93134…aaef

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xc36fa358…24cb

0x34b655…2a6f

6 touches
3 conflicts

0xd99b3b64…1c95

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0001

0xc1ff9f…b0fc

6 touches
3 conflicts

0x2d7ea048…d78e

0x34b655…2a6f

4 touches
1 conflict

0x3be29374…1df9

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

3 conflicts on slot 0x0f6666e640…06f280

← previous block·next block →recent activity