← previous blocknext block →recent activity

Analyzing

Block #75,096,238

13 transactions · 12 stateful · 2026-05-17 02:50:37 UTC

Parallelism

62/100

Blocked

50%

Avg conflicts / tx

0.85

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,096,238  ·  13 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0xc6f57b7f…adca

0x065c9d…c394

6 touches
3 conflicts

0x16231249…036d

0x065c9d…c394

6 touches
3 conflicts

0xf6ddd2b3…38f7

0x065c9d…c394

5 touches
3 conflicts

0x389ef3cb…1db2

0x065c9d…c394

4 touches
1 conflict

0xb1aa8eba…ba51

0x065c9d…c394

4 touches
1 conflict

0x57f62bd7…58fd

0x065c9d…c394

4 touches
1 conflict

0xfcb7b8b2…ebb3

0x065c9d…c394

4 touches
1 conflict

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity