← previous blocknext block →recent activity

Analyzing

Block #73,212,034

13 transactions · 11 stateful · 2026-05-08 09:15:20 UTC

Parallelism

77/100

Blocked

27%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,212,034  ·  13 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

0x7f189cf6…afab

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x25de453d…9573

0x34b655…2a6f

4 touches
1 conflict

0x3b3a5945…10d0

0x34b655…2a6f

4 touches
1 conflict

0x108394d8…4411

0x34b655…2a6f

4 touches
1 conflict

0x9e52eba4…6b28

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

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: 0x065c9d28…a9c394

3 conflicts on slot 0x7f189cf621…beafab

← previous block·next block →recent activity