← previous blocknext block →recent activity

Analyzing

Block #75,511,649

13 transactions · 5 stateful · 2026-05-19 01:12:25 UTC

Parallelism

85/100

Blocked

20%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,511,649  ·  13 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

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0x5f738d40…ed19

0x065c9d…c394

2 touches
0 conflicts

0x2f88a23f…9dc5

0x2a68ba…90c5

2 touches
0 conflicts

0x99a21305…dffc

0x2a68ba…90c5

2 touches
0 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

2 touches
0 conflicts

0x4bef88e0…eaca

0x3bd359…433a

2 touches
0 conflicts

0xf8127de7…d5ec

0x3bd359…433a

2 touches
0 conflicts

0x5b4b3fa7…2f73

0x754704…b603

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

1 conflict on slot 0x443a3e479f…3af4a4

← previous block·next block →recent activity