← previous blocknext block →recent activity

Analyzing

Block #87,410,840

16 transactions · 14 stateful · 2026-07-13 04:14:43 UTC

Parallelism

75/100

Blocked

50%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,410,840  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xc36fa358…24cb

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x09500602…94ea

0x34b655…2a6f

4 touches
1 conflict

0x10efb0c1…2ddc

0x34b655…2a6f

4 touches
1 conflict

0x1eb0fab5…3517

0x34b655…2a6f

4 touches
1 conflict

0x6b22f8eb…68cb

0x34b655…2a6f

4 touches
1 conflict

0x734ee320…caae

0x34b655…2a6f

4 touches
1 conflict

0x7c46fde6…d6a0

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 0xc36fa35805…6f24cb

← previous block·next block →recent activity