← previous blocknext block →recent activity

Analyzing

Block #75,099,440

8 transactions · 7 stateful · 2026-05-17 03:12:00 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,099,440  ·  8 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

0x356d6092…f505

0x065c9d…c394

4 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0c7eb777…4138

0x065c9d…c394

2 touches
0 conflicts

0x107960c7…bfd0

0x065c9d…c394

2 touches
0 conflicts

0x20c81642…9d7c

0x065c9d…c394

2 touches
0 conflicts

0xcfb09b57…c686

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 0x356d6092d2…86f505

← previous block·next block →recent activity