← previous blocknext block →recent activity

Analyzing

Block #87,593,470

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

Parallelism

78/100

Blocked

41%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,593,470  ·  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

0xc6ed530e…fa7d

0x34b655…2a6f

6 touches
3 conflicts

0xc807a400…b958

0x34b655…2a6f

6 touches
3 conflicts

0xcfcb8911…e9da

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x68edd6ac…8c3c

0x34b655…2a6f

4 touches
1 conflict

0x6d11d4a8…3a2d

0x34b655…2a6f

4 touches
1 conflict

0x7ca05570…8220

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 0xc6ed530ecc…a9fa7d

← previous block·next block →recent activity