← previous blocknext block →recent activity

Analyzing

Block #75,505,926

10 transactions · 10 stateful · 2026-05-19 00:33:08 UTC

Parallelism

80/100

Blocked

10%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,505,926  ·  10 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x05eb7aa5…fd8f

0x065c9d…c394

2 touches
0 conflicts

0x06a3e0ac…9874

0x065c9d…c394

2 touches
0 conflicts

0x4aacaeae…80e0

0x065c9d…c394

2 touches
0 conflicts

0x96309dab…a309

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

1 conflict on slot 0x443a3e479f…3af4a4

← previous block·next block →recent activity