← previous blocknext block →recent activity

Analyzing

Block #75,233,020

20 transactions · 17 stateful · 2026-05-17 18:03:52 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

1.35

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #75,233,020  ·  20 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

0x17606ba6…1b6e

0x754704…b603

12 touches
15 conflicts

0x0d0b2509…074d

0x3bd359…433a

10 touches
10 conflicts

0xe6455d1f…1029

0x754704…b603

10 touches
10 conflicts

0x3e49348b…9445

0x34b655…2a6f

6 touches
3 conflicts

0xe75ce681…ba60

0x188d58…ea8e

6 touches
3 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

6 touches
3 conflicts

0x0dbf9688…c6cf

0xd18b7e…414b

6 touches
3 conflicts

0x12309510…0ac2

0x000000…012a

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: 0x754704bc…afb603

15 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity