← previous blocknext block →recent activity

Analyzing

Block #73,918,972

13 transactions · 9 stateful · 2026-05-11 15:56:07 UTC

Parallelism

77/100

Blocked

56%

Avg conflicts / tx

0.46

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,918,972  ·  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

0x5de96bd3…c60c

0x34b655…2a6f

6 touches
3 conflicts

0x3a469c7a…db41

0x34b655…2a6f

6 touches
3 conflicts

0xf6167ec5…99fe

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb81

0x1b6862…e19c

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

3 conflicts on slot 0x5de96bd34a…ecc60c

← previous block·next block →recent activity