← previous blocknext block →recent activity

Analyzing

Block #99,320,628

18 transactions · 18 stateful · 2026-08-26 11:46:30 UTC

Parallelism

61/100

Blocked

44%

Avg conflicts / tx

0.94

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #99,320,628  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x53f7214d…8ec6

0x34b655…2a6f

6 touches
3 conflicts

0xea2eef12…dd5a

0x34b655…2a6f

4 touches
1 conflict

0x40b42f88…fa3b

0x065c9d…c394

4 touches
1 conflict

0x1a2055c7…9054

0x34b655…2a6f

4 touches
1 conflict

0x54941b94…3d80

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity