← previous blocknext block →recent activity

Analyzing

Block #73,815,241

12 transactions · 9 stateful · 2026-05-11 04:24:59 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,815,241  ·  12 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

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x07e1d521…fc32

0x34b655…2a6f

2 touches
0 conflicts

0x1e75fe8b…59f8

0x34b655…2a6f

2 touches
0 conflicts

0x23b2399c…6e4b

0x34b655…2a6f

2 touches
0 conflicts

0x375b6201…9c1e

0x34b655…2a6f

2 touches
0 conflicts

0x3a429191…9cda

0x34b655…2a6f

2 touches
0 conflicts

0x4f3a6b4a…3819

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

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity