← previous blocknext block →recent activity

Analyzing

Block #75,106,770

12 transactions · 10 stateful · 2026-05-17 04:00:56 UTC

Parallelism

67/100

Blocked

60%

Avg conflicts / tx

0.83

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,106,770  ·  12 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

0x348fda08…7e96

0x065c9d…c394

6 touches
3 conflicts

0xba38536d…2b7d

0x065c9d…c394

6 touches
3 conflicts

0x631b4113…baa9

0x34b655…2a6f

6 touches
3 conflicts

0xe9bfd410…fa18

0x065c9d…c394

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x1a3145c4…e0f6

0x065c9d…c394

4 touches
1 conflict

0x1c314424…9a0c

0x065c9d…c394

4 touches
1 conflict

0x70adc621…80c4

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

3 conflicts on slot 0x348fda08cf…fc7e96

← previous block·next block →recent activity