← previous blocknext block →recent activity

Analyzing

Block #87,699,100

19 transactions · 19 stateful · 2026-07-14 12:22:52 UTC

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

0.74

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,699,100  ·  19 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

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0xc36fa358…24cb

0x34b655…2a6f

6 touches
3 conflicts

0x369883e3…a449

0x34b655…2a6f

6 touches
3 conflicts

0x731f1834…ef5f

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4ab

0x34b655…2a6f

4 touches
1 conflict

0x86b36626…cd70

0x34b655…2a6f

4 touches
1 conflict

0x86b36626…cd71

0x34b655…2a6f

4 touches
1 conflict

0x8cc1393f…07fb

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

10 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity