← previous blocknext block →recent activity

Analyzing

Block #73,868,134

15 transactions · 15 stateful · 2026-05-11 10:17:26 UTC

Parallelism

60/100

Blocked

53%

Avg conflicts / tx

1.27

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,868,134  ·  15 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

0xb159af88…a9e7

0x065c9d…c394

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…0007

0x1414f3…5137

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xe6455d1f…1029

0x754704…b603

4 touches
1 conflict

0x0d0b2509…074d

0x3bd359…433a

4 touches
1 conflict

0x7f81fb82…633e

0x065c9d…c394

2 touches
0 conflicts

0x12e26938…5d6f

0x065c9d…c394

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

15 conflicts on slot 0xb159af880b…47a9e7

← previous block·next block →recent activity