← previous blocknext block →recent activity

Analyzing

Block #73,987,151

10 transactions · 8 stateful · 2026-05-11 23:30:47 UTC

Parallelism

70/100

Blocked

38%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,987,151  ·  10 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

0xf6476f21…3580

0x34b655…2a6f

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x28933977…81c5

0x34b655…2a6f

4 touches
1 conflict

0x4f36dfed…2741

0x34b655…2a6f

4 touches
1 conflict

0x5d6559c4…f3c7

0x34b655…2a6f

4 touches
1 conflict

0x7af57d48…189f

0x34b655…2a6f

4 touches
1 conflict

0x7ee110ef…8394

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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

1 conflict on slot 0xf6476f21e7…f83580

← previous block·next block →recent activity