← previous blocknext block →recent activity

Analyzing

Block #87,362,739

18 transactions · 16 stateful · 2026-07-12 22:52:54 UTC

Parallelism

72/100

Blocked

56%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,362,739  ·  18 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

0x93b6fab0…09d6

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x27a78688…b891

0x34b655…2a6f

4 touches
1 conflict

0x3d4584df…ffed

0x34b655…2a6f

4 touches
1 conflict

0x427f51fd…bd80

0x34b655…2a6f

4 touches
1 conflict

0x428f1a03…804c

0x34b655…2a6f

4 touches
1 conflict

0x505b37d8…d3fc

0x34b655…2a6f

4 touches
1 conflict

0x511ecf07…8ed0

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

6 conflicts on slot 0x93b6fab01a…2d09d6

← previous block·next block →recent activity