← previous blocknext block →recent activity

Analyzing

Block #75,689,642

12 transactions · 9 stateful · 2026-05-19 21:02:00 UTC

Parallelism

83/100

Blocked

11%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,689,642  ·  12 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xcc4f1f14…aa5f

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x168e3d0c…6fdb

0x065c9d…c394

2 touches
0 conflicts

0x5daf4d4e…d984

0x065c9d…c394

2 touches
0 conflicts

0x6c51f5c8…f58c

0x065c9d…c394

2 touches
0 conflicts

0x738f9f07…994f

0x065c9d…c394

2 touches
0 conflicts

0x791358e5…5a01

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity