← previous blocknext block →recent activity

Analyzing

Block #73,968,474

14 transactions · 11 stateful · 2026-05-11 21:25:22 UTC

Parallelism

50/100

Blocked

55%

Avg conflicts / tx

1.86

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,968,474  ·  14 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0xf537eaa0…73c8

0x065c9d…c394

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x6f08361d…bda6

0x065c9d…c394

2 touches
0 conflicts

0xe9d6549f…44f7

0x065c9d…c394

2 touches
0 conflicts

0xc3006de0…9726

0x188d58…ea8e

2 touches
0 conflicts

0xc3006de0…9727

0x188d58…ea8e

2 touches
0 conflicts

0x05eea3e3…5846

0x2a68ba…90c5

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

21 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity