← previous blocknext block →recent activity

Analyzing

Block #97,627,547

22 transactions · 20 stateful · 2026-08-20 12:39:50 UTC

Parallelism

77/100

Blocked

35%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,627,547  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xb12a9ddc…2533

0x34b655…2a6f

6 touches
3 conflicts

0x0153b05d…a2d8

0x34b655…2a6f

6 touches
3 conflicts

0x3f4f9f22…8ad6

0x34b655…2a6f

4 touches
1 conflict

0x3f4f9f22…8ad7

0x34b655…2a6f

4 touches
1 conflict

0x49890ced…6f23

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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

10 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity