← previous blocknext block →recent activity

Analyzing

Block #73,261,129

11 transactions · 10 stateful · 2026-05-08 14:41:51 UTC

Parallelism

73/100

Blocked

30%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,261,129  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xc824469a…641c

0x34b655…2a6f

4 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0x92339d95…0800

0x0000a8…8888

2 touches
0 conflicts

0x2ab27f89…eb24

0x065c9d…c394

2 touches
0 conflicts

0x03a40943…4d6b

0x34b655…2a6f

2 touches
0 conflicts

0x3384af2a…cab7

0x34b655…2a6f

2 touches
0 conflicts

0x87a380d9…2d04

0x34b655…2a6f

2 touches
0 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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity