← previous blocknext block →recent activity

Analyzing

Block #87,418,737

21 transactions · 21 stateful · 2026-07-13 05:07:31 UTC

Parallelism

81/100

Blocked

43%

Avg conflicts / tx

0.76

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,418,737  ·  21 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

0x5b353877…605d

0x34b655…2a6f

8 touches
6 conflicts

0x0a57a2b8…3cdd

0x34b655…2a6f

6 touches
3 conflicts

0x114a5fe9…8d41

0x34b655…2a6f

6 touches
3 conflicts

0x16b3a441…13db

0x34b655…2a6f

6 touches
3 conflicts

0x922c7ebd…6600

0xc8689a…ee79

6 touches
3 conflicts

0xd6fbd59c…2646

0x34b655…2a6f

6 touches
3 conflicts

0xe47478a3…a058

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

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

6 conflicts on slot 0x5b353877fb…57605d

← previous block·next block →recent activity