← previous blocknext block →recent activity

Analyzing

Block #87,910,182

19 transactions · 18 stateful · 2026-07-15 11:55:12 UTC

Parallelism

74/100

Blocked

39%

Avg conflicts / tx

0.84

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,910,182  ·  19 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

0x0f6666e6…f280

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xc36fa358…24cb

0x34b655…2a6f

8 touches
6 conflicts

0xf28cf8dc…b0ca

0x34b655…2a6f

6 touches
3 conflicts

0x4e815ddc…2f85

0x34b655…2a6f

4 touches
1 conflict

0x8743e1ba…8331

0x34b655…2a6f

4 touches
1 conflict

0x9068a9bc…86ee

0x34b655…2a6f

4 touches
1 conflict

0x9666da3b…0f0e

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 0x0f6666e640…06f280

← previous block·next block →recent activity