← previous blocknext block →recent activity

Analyzing

Block #88,365,998

18 transactions · 17 stateful · 2026-07-17 14:45:26 UTC

Parallelism

61/100

Blocked

53%

Avg conflicts / tx

1.11

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #88,365,998  ·  18 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

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0x92385428…6941

0x34b655…2a6f

10 touches
10 conflicts

0x427d1120…4eb1

0x34b655…2a6f

8 touches
6 conflicts

0x2d651956…12e8

0x34b655…2a6f

6 touches
3 conflicts

0x5ef698c5…5ce4

0x34b655…2a6f

6 touches
3 conflicts

0x81e1b637…2b3c

0x34b655…2a6f

4 touches
1 conflict

0x8391fb68…4c83

0x34b655…2a6f

4 touches
1 conflict

0x88fb89dd…f591

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

10 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity