← previous blocknext block →recent activity

Analyzing

Block #87,295,634

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

Parallelism

68/100

Blocked

44%

Avg conflicts / tx

0.82

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,295,634  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xfaef08b1…0696

0x34b655…2a6f

10 touches
10 conflicts

0x8a35acfb…d1ac

0xb1dbf0…c0d3

10 touches
10 conflicts

0x8a35acfb…d1ad

0xb1dbf0…c0d3

7 touches
6 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7525206c…fbd5

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x974c36fe…1cd7

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

10 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity