← previous blocknext block →recent activity

Analyzing

Block #87,612,138

25 transactions · 16 stateful · 2026-07-14 02:41:38 UTC

Parallelism

84/100

Blocked

38%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,612,138  ·  25 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

0x0a6ba3b4…2123

0x34b655…2a6f

6 touches
3 conflicts

0xcfcb8911…e9da

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xd93edb3f…94ec

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x70040326…40e5

0x34b655…2a6f

4 touches
1 conflict

0x9599eb41…b5d6

0x34b655…2a6f

4 touches
1 conflict

0x9f6c1915…6b86

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 0x0a6ba3b47a…852123

← previous block·next block →recent activity