← previous blocknext block →recent activity

Analyzing

Block #75,103,189

12 transactions · 9 stateful · 2026-05-17 03:36:59 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,103,189  ·  12 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xa7e3ceaa…baa7

0x065c9d…c394

4 touches
1 conflict

0x631b4113…baa9

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x348fda08…7e96

0x065c9d…c394

4 touches
1 conflict

0x17972387…9ce4

0x065c9d…c394

2 touches
0 conflicts

0x194921ef…f6e8

0x065c9d…c394

2 touches
0 conflicts

0x53ce0d98…d61e

0x065c9d…c394

2 touches
0 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

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 0xa7e3ceaaf2…5bbaa7

← previous block·next block →recent activity