← previous blocknext block →recent activity

Analyzing

Block #73,868,219

16 transactions · 14 stateful · 2026-05-11 10:18:00 UTC

Parallelism

69/100

Blocked

64%

Avg conflicts / tx

1.19

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,868,219  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x2ed00f98…da9f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x31ed1958…817e

0x065c9d…c394

6 touches
3 conflicts

0x7f81fb82…633e

0x065c9d…c394

6 touches
3 conflicts

0xb159af88…a9e7

0x065c9d…c394

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xe96c91d2…32ff

0x8d66a4…3095

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: 0x065c9d28…a9c394

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity