← previous blocknext block →recent activity

Analyzing

Block #88,091,099

20 transactions · 19 stateful · 2026-07-16 08:05:14 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

0.8

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #88,091,099  ·  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

0x2b5101ac…090b

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x45ea7a97…bbb3

0x34b655…2a6f

4 touches
1 conflict

0x461428a9…24b2

0x34b655…2a6f

4 touches
1 conflict

0x461428a9…24b3

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x7e17e82a…9748

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 0x2b5101acd1…7c090b

← previous block·next block →recent activity