← previous blocknext block →recent activity

Analyzing

Block #88,086,072

19 transactions · 18 stateful · 2026-07-16 07:31:37 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #88,086,072  ·  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

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x5cebb016…c149

0x34b655…2a6f

6 touches
3 conflicts

0xcc13c07b…d7cc

0x34b655…2a6f

6 touches
3 conflicts

0xf4f9cac7…fd98

0x34b655…2a6f

6 touches
3 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64dc

0x34b655…2a6f

4 touches
1 conflict

0xbf78ee7f…e7fd

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity