← previous blocknext block →recent activity

Analyzing

Block #87,613,132

22 transactions · 19 stateful · 2026-07-14 02:48:18 UTC

Parallelism

73/100

Blocked

42%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,613,132  ·  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

0x92385428…6941

0x34b655…2a6f

12 touches
15 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0x9aaca373…d7c0

0x34b655…2a6f

6 touches
3 conflicts

0x4c188934…158e

0x34b655…2a6f

6 touches
3 conflicts

0x973729b4…d3fb

0x34b655…2a6f

6 touches
3 conflicts

0x2a5bc5cd…0a17

0x34b655…2a6f

4 touches
1 conflict

0x2b5101ac…090b

0x34b655…2a6f

4 touches
1 conflict

0x3c8d99a5…b937

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

15 conflicts on slot 0x92385428ad…dc6941

← previous block·next block →recent activity