← previous blocknext block →recent activity

Analyzing

Block #98,675,812

27 transactions · 24 stateful · 2026-08-24 05:31:31 UTC

Parallelism

59/100

Blocked

54%

Avg conflicts / tx

1.52

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #98,675,812  ·  27 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x482471ad…122f

0x34b655…2a6f

16 touches
28 conflicts

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x074c08f8…fb56

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x00d67843…2809

0x34b655…2a6f

6 touches
3 conflicts

0x705ab4ae…0162

0x34b655…2a6f

6 touches
3 conflicts

0x70f44f70…6f45

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

28 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity