← previous blocknext block →recent activity

Analyzing

Block #75,688,213

9 transactions · 7 stateful · 2026-05-19 20:52:34 UTC

Parallelism

67/100

Blocked

43%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,688,213  ·  9 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xdfa159d0…1576

0x065c9d…c394

4 touches
1 conflict

0xcc4f1f14…aa5f

0x065c9d…c394

4 touches
1 conflict

0x5153c3a6…5777

0x065c9d…c394

4 touches
1 conflict

0xfc56a8aa…6666

0x065c9d…c394

3 touches
1 conflict

0xe809b79a…b454

0x065c9d…c394

3 touches
1 conflict

0xa605468c…1bfc

0x1d1325…2305

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

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity