← previous blocknext block →recent activity

Analyzing

Block #75,329,630

13 transactions · 8 stateful · 2026-05-18 04:50:21 UTC

Parallelism

85/100

Blocked

25%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,329,630  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xc2dcae98…1617

0x065c9d…c394

4 touches
1 conflict

0xb897b2d2…4a77

0x065c9d…c394

3 touches
1 conflict

0x813ace0f…05b0

0x065c9d…c394

3 touches
1 conflict

0x1a894849…f653

0x065c9d…c394

2 touches
0 conflicts

0x1c824c97…40ed

0x065c9d…c394

2 touches
0 conflicts

0x443a3e47…f4a4

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