← previous blocknext block →recent activity

Analyzing

Block #75,137,215

36 transactions · 23 stateful · 2026-05-17 07:24:01 UTC

Parallelism

81/100

Blocked

48%

Avg conflicts / tx

0.75

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #75,137,215  ·  36 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

0x31e678d4…41d3

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0000

0xd5b70d…615b

4 touches
1 conflict

0x00000000…0002

0xd5b70d…615b

4 touches
1 conflict

0x00000000…0004

0xd5b70d…615b

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x348fda08…7e96

0x065c9d…c394

4 touches
1 conflict

0xba38536d…2b7d

0x065c9d…c394

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

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: 0xd32edf66…9fff58

21 conflicts on slot 0x31e678d429…e541d3

← previous block·next block →recent activity