← previous blocknext block →recent activity

Analyzing

Block #88,081,586

24 transactions · 23 stateful · 2026-07-16 07:01:37 UTC

Parallelism

88/100

Blocked

26%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #88,081,586  ·  24 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x58620f29…db5a

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd8834cf3…0004

0x34b655…2a6f

6 touches
3 conflicts

0x5502e1cc…3910

0x34b655…2a6f

4 touches
1 conflict

0x5571e830…9cea

0x34b655…2a6f

4 touches
1 conflict

0x5777bd87…71bd

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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 0x58620f2942…18db5a

← previous block·next block →recent activity