← previous blocknext block →recent activity

Analyzing

Block #88,093,133

22 transactions · 19 stateful · 2026-07-16 08:18:51 UTC

Parallelism

68/100

Blocked

42%

Avg conflicts / tx

0.86

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #88,093,133  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x6f1a10f8…5a04

0x34b655…2a6f

6 touches
3 conflicts

0xc6b1d981…1be2

0xa6afd3…d132

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x6fbc2e5a…e69c

0x34b655…2a6f

4 touches
1 conflict

0x7b3f8378…b37d

0x34b655…2a6f

4 touches
1 conflict

0x8d989c17…e984

0x34b655…2a6f

4 touches
1 conflict

0xd99b3b64…1c95

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity