← previous blocknext block →recent activity

Analyzing

Block #73,923,840

17 transactions · 16 stateful · 2026-05-11 16:28:31 UTC

Parallelism

82/100

Blocked

44%

Avg conflicts / tx

0.59

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,923,840  ·  17 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x6f08361d…bda6

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x3187fda9…57d9

0x34b655…2a6f

6 touches
3 conflicts

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xb409e204…89ac

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

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity