← previous blocknext block →recent activity

Analyzing

Block #75,514,093

17 transactions · 10 stateful · 2026-05-19 01:29:10 UTC

Parallelism

82/100

Blocked

20%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,514,093  ·  17 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

0x892daf6e…48d8

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xb252cef0…acf9

0x065c9d…c394

3 touches
1 conflict

0x1567ae42…cadf

0x065c9d…c394

2 touches
0 conflicts

0xc31d1459…16a3

0x065c9d…c394

2 touches
0 conflicts

0xd1ac190a…cfd0

0x065c9d…c394

2 touches
0 conflicts

0xefe97ba7…1b21

0x065c9d…c394

2 touches
0 conflicts

0xfb5ce6c3…0992

0x065c9d…c394

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: 0x065c9d28…a9c394

3 conflicts on slot 0x892daf6e5d…6d48d8

← previous block·next block →recent activity