← previous blocknext block →recent activity

Analyzing

Block #87,786,545

20 transactions · 18 stateful · 2026-07-14 22:08:15 UTC

Parallelism

80/100

Blocked

44%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,786,545  ·  20 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

0x4acbdbcf…a8c6

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x03cb2ce9…7c43

0x34b655…2a6f

4 touches
1 conflict

0x06571a69…0512

0x34b655…2a6f

4 touches
1 conflict

0x0dd44476…ef40

0x34b655…2a6f

4 touches
1 conflict

0x15b254ac…664f

0x34b655…2a6f

4 touches
1 conflict

0x242fd968…26ed

0x34b655…2a6f

4 touches
1 conflict

0x3469d149…0afb

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 0x4acbdbcf7f…d0a8c6

← previous block·next block →recent activity