← previous blocknext block →recent activity

Analyzing

Block #87,711,891

18 transactions · 18 stateful · 2026-07-14 13:48:41 UTC

Parallelism

72/100

Blocked

39%

Avg conflicts / tx

0.56

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,711,891  ·  18 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

0x560ed681…07e6

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x7bc81250…725f

0x34b655…2a6f

4 touches
1 conflict

0x849cb897…43de

0x34b655…2a6f

4 touches
1 conflict

0xbe9baf16…df37

0x34b655…2a6f

4 touches
1 conflict

0xbf78ee7f…e7fd

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 0x560ed68159…1e07e6

← previous block·next block →recent activity