← previous blocknext block →recent activity

Analyzing

Block #87,455,074

26 transactions · 19 stateful · 2026-07-13 09:10:26 UTC

Parallelism

85/100

Blocked

37%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,455,074  ·  26 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

0x9b02ba92…7100

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x7aad02c6…b979

0x34b655…2a6f

4 touches
1 conflict

0x8a28033c…5ff0

0x34b655…2a6f

4 touches
1 conflict

0x8fe37a3f…4c89

0x34b655…2a6f

4 touches
1 conflict

0xb568bd0a…0a72

0x34b655…2a6f

4 touches
1 conflict

0xb568bd0a…0a73

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 0x9b02ba92fc…e87100

← previous block·next block →recent activity