← previous blocknext block →recent activity

Analyzing

Block #97,545,025

20 transactions · 16 stateful · 2026-08-20 05:41:39 UTC

Parallelism

80/100

Blocked

44%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,545,025  ·  20 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

0xea1d91a3…b583

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0007

0xc1570a…c91b

4 touches
1 conflict

0xffc26b06…715f

0x34b655…2a6f

4 touches
1 conflict

0xffc26b06…715e

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x41e3f022…1f03

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5cfec795…7c0e

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 0xea1d91a39b…86b583

← previous block·next block →recent activity