← previous blocknext block →recent activity

Analyzing

Block #75,124,546

13 transactions · 11 stateful · 2026-05-17 05:59:33 UTC

Parallelism

69/100

Blocked

27%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,124,546  ·  13 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x06ac26e1…60c0

0x065c9d…c394

4 touches
1 conflict

0x55a375f4…a478

0x065c9d…c394

4 touches
1 conflict

0x0c6e3066…3f55

0x065c9d…c394

3 touches
1 conflict

0xfa978bd6…2d7e

0x065c9d…c394

3 touches
1 conflict

0x64226390…74a4

0x065c9d…c394

3 touches
1 conflict

0xf0814662…60be

0x065c9d…c394

3 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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity