← previous blocknext block →recent activity

Analyzing

Block #97,612,818

21 transactions · 21 stateful · 2026-08-20 11:25:43 UTC

Parallelism

52/100

Blocked

57%

Avg conflicts / tx

2.1

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #97,612,818  ·  21 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x322346fc…a162

0x34b655…2a6f

12 touches
15 conflicts

0x88724b87…5e65

0x34b655…2a6f

12 touches
15 conflicts

0x7de57974…f5ba

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x1d351a9b…f2dd

0x34b655…2a6f

6 touches
3 conflicts

0x1cdfe548…d3aa

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

15 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity