← previous blocknext block →recent activity

Analyzing

Block #97,613,825

21 transactions · 21 stateful · 2026-08-20 11:30:47 UTC

Parallelism

52/100

Blocked

62%

Avg conflicts / tx

1.62

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #97,613,825  ·  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

0x88724b87…5e65

0x34b655…2a6f

16 touches
28 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x9981b229…adcd

0x34b655…2a6f

8 touches
6 conflicts

0x27e04087…eb03

0x34b655…2a6f

8 touches
6 conflicts

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0x333300cc…04fe

0x34b655…2a6f

6 touches
3 conflicts

0x948836ff…59ab

0x34b655…2a6f

6 touches
3 conflicts

0xe21a94dd…4838

0x34b655…2a6f

4 touches
2 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 0x88724b8763…1a5e65

← previous block·next block →recent activity