← previous blocknext block →recent activity

Analyzing

Block #97,480,159

25 transactions · 25 stateful · 2026-08-20 00:15:21 UTC

Parallelism

76/100

Blocked

36%

Avg conflicts / tx

0.76

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #97,480,159  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xda1f3e2c…b73d

0x34b655…2a6f

10 touches
10 conflicts

0xf1125f34…3231

0xa6afd3…d132

6 touches
3 conflicts

0x6737ee07…9978

0x34b655…2a6f

6 touches
3 conflicts

0x0e416bf8…0cb7

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x53dcbe77…b8e8

0x34b655…2a6f

4 touches
1 conflict

0x62030a81…91be

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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 0xda1f3e2ca4…a6b73d

← previous block·next block →recent activity