← previous blocknext block →recent activity

Analyzing

Block #73,202,717

18 transactions · 15 stateful · 2026-05-08 08:13:26 UTC

Parallelism

83/100

Blocked

20%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,202,717  ·  18 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

0x3b8ffd61…f3ad

0x34b655…2a6f

6 touches
3 conflicts

0x7f189cf6…afab

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x1ee7a8f7…87f4

0x34b655…2a6f

4 touches
1 conflict

0x71f8ae96…161f

0x34b655…2a6f

4 touches
1 conflict

0xec9f9e3d…4858

0x34b655…2a6f

4 touches
1 conflict

0x3b064566…a80a

0x065c9d…c394

2 touches
0 conflicts

0x50a5a032…1f21

0x065c9d…c394

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

3 conflicts on slot 0x3b8ffd6160…92f3ad

← previous block·next block →recent activity