← previous blocknext block →recent activity

Analyzing

Block #99,491,063

17 transactions · 15 stateful · 2026-08-27 02:04:45 UTC

Parallelism

53/100

Blocked

67%

Avg conflicts / tx

1.65

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #99,491,063  ·  17 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xfc8d572c…b27d

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xa2042b9b…0ecb

0x34b655…2a6f

8 touches
6 conflicts

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x53103bb4…02a1

0x34b655…2a6f

8 touches
6 conflicts

0x93afca4c…b478

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

15 conflicts on slot 0xfc8d572cb3…e5b27d

← previous block·next block →recent activity