← previous blocknext block →recent activity

Analyzing

Block #75,502,217

14 transactions · 13 stateful · 2026-05-19 00:07:42 UTC

Parallelism

86/100

Blocked

23%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,502,217  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x99a21305…dffc

0x2a68ba…90c5

4 touches
1 conflict

0x2796c028…023b

0x34b655…2a6f

4 touches
1 conflict

0x5086c64a…28ba

0x34b655…2a6f

4 touches
1 conflict

0x32bf75a2…023a

0x065c9d…c394

3 touches
1 conflict

0xd5c5b4f6…7ab5

0xd32edf…ff58

3 touches
1 conflict

0x489cb750…7069

0x065c9d…c394

2 touches
0 conflicts

0x892daf6e…48d8

0x065c9d…c394

2 touches
0 conflicts

0x06e40499…165e

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 0x99a2130578…57dffc

← previous block·next block →recent activity