← previous blocknext block →recent activity

Analyzing

Block #73,807,293

9 transactions · 7 stateful · 2026-05-11 03:32:09 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,807,293  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x5de96bd3…c60c

0x34b655…2a6f

4 touches
1 conflict

0x99120c08…ee84

0x34b655…2a6f

4 touches
1 conflict

0xb1632c2f…d991

0x0a3323…0a3c

2 touches
0 conflicts

0xe76b6197…f6d9

0x0a3323…0a3c

2 touches
0 conflicts

0x1f9e4688…bf1b

0x188d58…ea8e

2 touches
0 conflicts

0x1f9e4688…bf1c

0x188d58…ea8e

2 touches
0 conflicts

0x63f5c02f…6853

0x3bd359…433a

2 touches
0 conflicts

0x80c5bffd…46e2

0x3bd359…433a

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

1 conflict on slot 0x5de96bd34a…ecc60c

← previous block·next block →recent activity