← previous blocknext block →recent activity

Analyzing

Block #73,869,253

24 transactions · 14 stateful · 2026-05-11 10:24:53 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

0.92

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,869,253  ·  24 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

0x00000000…0007

0x1414f3…5137

14 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x2ed6e329…5e08

0x0c65a0…0852

2 touches
0 conflicts

0x490911cc…5fea

0x0c65a0…0852

2 touches
0 conflicts

0x013acb15…cb30

0x1414f3…5137

2 touches
0 conflicts

0x048123dd…bbaf

0x1414f3…5137

2 touches
0 conflicts

0x4b58b312…0b42

0x1414f3…5137

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: 0x1414f3ba…045137

21 conflicts on slot 0x0000000000…000007

← previous block·next block →recent activity