← previous blocknext block →recent activity

Analyzing

Block #87,704,793

24 transactions · 19 stateful · 2026-07-14 13:01:10 UTC

Parallelism

83/100

Blocked

37%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,704,793  ·  24 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

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x8fe37a3f…4c89

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x41ebf7ed…f662

0x34b655…2a6f

4 touches
1 conflict

0x4560e5a8…b741

0x34b655…2a6f

4 touches
1 conflict

0x6323c5ea…ce8a

0x34b655…2a6f

4 touches
1 conflict

0x67905f6e…02a1

0x34b655…2a6f

4 touches
1 conflict

0x7837c02d…0965

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity