← previous blocknext block →recent activity

Analyzing

Block #87,699,865

21 transactions · 19 stateful · 2026-07-14 12:27:59 UTC

Parallelism

76/100

Blocked

42%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,699,865  ·  21 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

0x00000000…0001

0xc1ff9f…b0fc

6 touches
3 conflicts

0x53f393fa…00b9

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xc36fa358…24cb

0x34b655…2a6f

6 touches
3 conflicts

0xd6419ef2…1643

0x34b655…2a6f

6 touches
3 conflicts

0x35a9f06c…7689

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x2f537097…f2b6

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: 0xc1ff9fef…f4b0fc

3 conflicts on slot 0x0000000000…000001

← previous block·next block →recent activity