← previous blocknext block →recent activity

Analyzing

Block #88,087,391

20 transactions · 19 stateful · 2026-07-16 07:40:27 UTC

Parallelism

70/100

Blocked

47%

Avg conflicts / tx

0.85

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #88,087,391  ·  20 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

0x0a57a2b8…3cdd

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb1b21ea8…d790

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x736bfd85…2594

0x34b655…2a6f

6 touches
3 conflicts

0x7bcd679c…954d

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x9c2e6ea0…9df8

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 0x0a57a2b8cd…773cdd

← previous block·next block →recent activity