← previous blocknext block →recent activity

Analyzing

Block #87,295,671

19 transactions · 18 stateful · 2026-07-12 15:24:30 UTC

Parallelism

68/100

Blocked

44%

Avg conflicts / tx

0.68

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,295,671  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xdb564c7f…72f9

0x34b655…2a6f

6 touches
3 conflicts

0x45ea7a97…bbb3

0x34b655…2a6f

6 touches
3 conflicts

0x17f7e142…085e

0x34b655…2a6f

4 touches
1 conflict

0x3c3621c7…3e11

0x34b655…2a6f

4 touches
1 conflict

0x547cb072…92bf

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4ab

0x34b655…2a6f

4 touches
1 conflict

0x875c3459…2879

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity