← previous blocknext block →recent activity

Analyzing

Block #75,124,087

14 transactions · 13 stateful · 2026-05-17 05:56:32 UTC

Parallelism

71/100

Blocked

31%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,124,087  ·  14 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

0xba38536d…2b7d

0x065c9d…c394

8 touches
6 conflicts

0x348fda08…7e96

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2032c5a7…f5f7

0x065c9d…c394

4 touches
1 conflict

0x65c3b2cd…a1c9

0x065c9d…c394

4 touches
1 conflict

0x24b012db…e144

0x065c9d…c394

3 touches
1 conflict

0x80bf9fe0…b74c

0x065c9d…c394

3 touches
1 conflict

0x4249cee5…efb5

0x065c9d…c394

3 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 0xba38536db1…342b7d

← previous block·next block →recent activity