← previous blocknext block →recent activity

Analyzing

Block #73,297,250

11 transactions · 10 stateful · 2026-05-08 18:42:15 UTC

Parallelism

64/100

Blocked

40%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,297,250  ·  11 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

0x8a85cf3d…2868

0x34b655…2a6f

8 touches
6 conflicts

0x2fe4467b…dd70

0x34b655…2a6f

8 touches
6 conflicts

0x1b9e654e…0a08

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

8 touches
6 conflicts

0x6ddcb186…0578

0x34b655…2a6f

8 touches
6 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

8 touches
6 conflicts

0xd49762c9…1359

0x34b655…2a6f

8 touches
6 conflicts

0x7b50a82b…f53d

0x34b655…2a6f

6 touches
3 conflicts

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: 0x34b6552d…112a6f

6 conflicts on slot 0x8a85cf3dc8…792868

← previous block·next block →recent activity