← previous blocknext block →recent activity

Analyzing

Block #97,656,422

20 transactions · 18 stateful · 2026-08-20 15:09:30 UTC

Parallelism

65/100

Blocked

44%

Avg conflicts / tx

1.4

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #97,656,422  ·  20 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

0x482471ad…122f

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x3b3a5945…10d0

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x821c347d…aad6

0x34b655…2a6f

4 touches
1 conflict

0xa227f33f…c929

0x34b655…2a6f

4 touches
1 conflict

0xa9a9d0e0…4087

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

21 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity