← previous blocknext block →recent activity

Analyzing

Block #97,604,075

20 transactions · 17 stateful · 2026-08-20 10:41:10 UTC

Parallelism

65/100

Blocked

47%

Avg conflicts / tx

1.15

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #97,604,075  ·  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

12 touches
15 conflicts

0x35c84655…53e3

0x34b655…2a6f

6 touches
3 conflicts

0x82187006…4dc6

0x34b655…2a6f

6 touches
3 conflicts

0x6183ee9a…21b1

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0007

0xc1570a…c91b

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x741b46bb…1f42

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