← previous blocknext block →recent activity

Analyzing

Block #73,869,171

12 transactions · 10 stateful · 2026-05-11 10:24:20 UTC

Parallelism

67/100

Blocked

30%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,869,171  ·  12 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xb159af88…a9e7

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x02d95bf9…1089

0x065c9d…c394

2 touches
0 conflicts

0x413a05c0…fdf4

0x065c9d…c394

2 touches
0 conflicts

0xb3f13545…126c

0x065c9d…c394

2 touches
0 conflicts

0xc4864452…fc40

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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

3 conflicts on slot 0xb159af880b…47a9e7

← previous block·next block →recent activity