← previous blocknext block →recent activity

Analyzing

Block #73,654,106

13 transactions · 8 stateful · 2026-05-10 10:18:49 UTC

Parallelism

62/100

Blocked

50%

Avg conflicts / tx

0.77

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,654,106  ·  13 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0x0e8fc1aa…757a

0x386489…7508

2 touches
0 conflicts

0x31e052ed…3133

0x386489…7508

2 touches
0 conflicts

0x14847c98…036f

0x3ef3d8…d9ae

2 touches
0 conflicts

0x14847c98…0370

0x3ef3d8…d9ae

2 touches
0 conflicts

0x816a4e62…8afe

0x3ef3d8…d9ae

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

10 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity