← previous blocknext block →recent activity

Analyzing

Block #75,205,438

24 transactions · 19 stateful · 2026-05-17 14:59:42 UTC

Parallelism

83/100

Blocked

58%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,205,438  ·  24 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

0x0d0b2509…074d

0x3bd359…433a

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf06c2cf5…61bd

0x34b655…2a6f

6 touches
3 conflicts

0xe6455d1f…1029

0x754704…b603

6 touches
3 conflicts

0xdd9c71d3…f05c

0xd32edf…ff58

5 touches
3 conflicts

0xba5743c7…21c2

0x1b6862…e19c

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x309ef367…e8a1

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: 0x3bd359c1…15433a

3 conflicts on slot 0x0d0b2509ae…4b074d

← previous block·next block →recent activity