← previous blocknext block →recent activity

Analyzing

Block #97,478,152

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

Parallelism

67/100

Blocked

48%

Avg conflicts / tx

1.13

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #97,478,152  ·  24 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xb3fb9fb5…64db

0x34b655…2a6f

8 touches
6 conflicts

0x806c6904…3d63

0x34b655…2a6f

8 touches
6 conflicts

0x1dc86774…166a

0x34b655…2a6f

8 touches
6 conflicts

0x1e0cf9b1…e924

0x40c49f…2af0

6 touches
3 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0xda1f3e2c…b73d

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0x655aa1bb…138c

0x40c49f…2af0

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

6 conflicts on slot 0xb3fb9fb561…7664db

← previous block·next block →recent activity