← previous blocknext block →recent activity

Analyzing

Block #73,816,963

19 transactions · 13 stateful · 2026-05-11 04:36:29 UTC

Parallelism

68/100

Blocked

38%

Avg conflicts / tx

0.79

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,816,963  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x22e295f5…1bef

0x065c9d…c394

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x03a40943…4d6b

0x34b655…2a6f

2 touches
0 conflicts

0x0947e021…ee5a

0x34b655…2a6f

2 touches
0 conflicts

0x10919b39…307a

0x34b655…2a6f

2 touches
0 conflicts

0x28933977…81c5

0x34b655…2a6f

2 touches
0 conflicts

0x5a637007…71e0

0x34b655…2a6f

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

15 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity