← previous blocknext block →recent activity

Analyzing

Block #87,496,731

23 transactions · 17 stateful · 2026-07-13 13:49:00 UTC

Parallelism

78/100

Blocked

41%

Avg conflicts / tx

0.39

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,496,731  ·  23 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

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x42c7fd6d…fc6c

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x1d6ccfe1…0611

0x34b655…2a6f

4 touches
1 conflict

0x486aed2f…813b

0x34b655…2a6f

4 touches
1 conflict

0x4940bb84…4ec2

0x34b655…2a6f

4 touches
1 conflict

0x70f21062…b6f3

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 0xf3d10975b0…050d07

← previous block·next block →recent activity