← previous blocknext block →recent activity

Analyzing

Block #75,196,499

11 transactions · 10 stateful · 2026-05-17 13:59:58 UTC

Parallelism

82/100

Blocked

30%

Avg conflicts / tx

0.27

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,196,499  ·  11 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

0xea57afd0…4232

0x34b655…2a6f

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x98995bb2…ec32

0x065c9d…c394

3 touches
1 conflict

0x7a8b611c…af22

0x065c9d…c394

3 touches
1 conflict

0x2e266fcb…09c7

0x065c9d…c394

2 touches
0 conflicts

0x67175b08…6c82

0x065c9d…c394

2 touches
0 conflicts

0x890a7265…5428

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: 0x34b6552d…112a6f

1 conflict on slot 0xea57afd097…7f4232

← previous block·next block →recent activity