← previous blocknext block →recent activity

Analyzing

Block #97,494,683

24 transactions · 23 stateful · 2026-08-20 01:28:25 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,494,683  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x8902ba1f…f4b6

0x34b655…2a6f

6 touches
3 conflicts

0x1dc86774…166a

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0007

0xc1570a…c91b

4 touches
1 conflict

0x28f324ed…9db7

0x34b655…2a6f

4 touches
1 conflict

0x8329c51e…4064

0x34b655…2a6f

4 touches
1 conflict

0x8329c51e…4065

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64db

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

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

3 conflicts on slot 0x8902ba1fb5…70f4b6

← previous block·next block →recent activity