← previous blocknext block →recent activity

Analyzing

Block #75,096,554

14 transactions · 13 stateful · 2026-05-17 02:52:44 UTC

Parallelism

57/100

Blocked

46%

Avg conflicts / tx

0.71

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,096,554  ·  14 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xfcb7b8b2…ebb3

0x065c9d…c394

6 touches
3 conflicts

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x388f889f…a655

0x34b655…2a6f

4 touches
1 conflict

0x874f5c70…608f

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf06c2cf5…61bd

0x34b655…2a6f

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