← previous blocknext block →recent activity

Analyzing

Block #87,697,353

19 transactions · 17 stateful · 2026-07-14 12:11:09 UTC

Parallelism

79/100

Blocked

47%

Avg conflicts / tx

0.74

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,697,353  ·  19 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

0x42c7fd6d…fc6c

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x08330b36…ae29

0x34b655…2a6f

4 touches
1 conflict

0x4f51d069…d0b4

0x34b655…2a6f

4 touches
1 conflict

0x5e4b65e1…ebe1

0x34b655…2a6f

4 touches
1 conflict

0x82e3f65a…d23c

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 0x42c7fd6d32…0afc6c

← previous block·next block →recent activity