← previous blocknext block →recent activity

Analyzing

Block #88,160,271

22 transactions · 19 stateful · 2026-07-16 15:48:11 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

0.73

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #88,160,271  ·  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

0x51087f5a…61f7

0x34b655…2a6f

6 touches
3 conflicts

0x3345f48f…e90d

0x34b655…2a6f

6 touches
3 conflicts

0x93b6fab0…09d6

0x34b655…2a6f

6 touches
3 conflicts

0x52cef1b0…0e4e

0x34b655…2a6f

6 touches
3 conflicts

0x0f15f74f…8d71

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

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 0x51087f5abf…f061f7

← previous block·next block →recent activity