← previous blocknext block →recent activity

Analyzing

Block #75,097,721

17 transactions · 17 stateful · 2026-05-17 03:00:31 UTC

Parallelism

59/100

Blocked

53%

Avg conflicts / tx

1.12

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #75,097,721  ·  17 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xfcb7b8b2…ebb3

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x443a3e47…f4a4

0x065c9d…c394

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xbfe3d887…654f

0x065c9d…c394

5 touches
3 conflicts

0xd159b6e7…5cfb

0x34b655…2a6f

4 touches
1 conflict

0x502ffad0…c89b

0x065c9d…c394

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

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

10 conflicts on slot 0xfcb7b8b239…6bebb3

← previous block·next block →recent activity