← previous blocknext block →recent activity

Analyzing

Block #87,726,383

26 transactions · 25 stateful · 2026-07-14 15:25:47 UTC

Parallelism

81/100

Blocked

28%

Avg conflicts / tx

0.54

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,726,383  ·  26 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

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x24b221a9…cf50

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xc4de6652…13f4

0x34b655…2a6f

6 touches
3 conflicts

0x22e7ebfe…1293

0x34b655…2a6f

4 touches
1 conflict

0x58620f29…db5a

0x34b655…2a6f

4 touches
1 conflict

0x5ec64628…72e4

0x34b655…2a6f

4 touches
1 conflict

0x67905f6e…02a1

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity