← previous blocknext block →recent activity

Analyzing

Block #87,612,875

22 transactions · 19 stateful · 2026-07-14 02:46:34 UTC

Parallelism

73/100

Blocked

37%

Avg conflicts / tx

0.5

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,612,875  ·  22 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

0x4c188934…158e

0x34b655…2a6f

6 touches
3 conflicts

0x43bc2389…898f

0x34b655…2a6f

4 touches
1 conflict

0x63f8a50d…333b

0x34b655…2a6f

4 touches
1 conflict

0x69523dd3…faa2

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7527802e…2ba9

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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 0x4c18893450…c5158e

← previous block·next block →recent activity