← previous blocknext block →recent activity

Analyzing

Block #73,869,170

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

Parallelism

71/100

Blocked

55%

Avg conflicts / tx

0.86

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,869,170  ·  14 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

0x00000000…0007

0x1414f3…5137

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xa56e58ca…36e5

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x9ec219b1…b3af

0x065c9d…c394

3 touches
1 conflict

0x25296f9e…7d7c

0x065c9d…c394

3 touches
1 conflict

0x62119758…2413

0x065c9d…c394

3 touches
1 conflict

0x80d8b017…ce61

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

6 conflicts on slot 0x0000000000…000007

← previous block·next block →recent activity