← previous blocknext block →recent activity

Analyzing

Block #75,307,306

10 transactions · 8 stateful · 2026-05-18 02:21:00 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,307,306  ·  10 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

0xcb45d9d6…cb85

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0x5bc3cf50…5474

0xd32edf…ff58

3 touches
1 conflict

0x1c1a981e…f3da

0xea1b8e…c5ec

2 touches
0 conflicts

0x263ef9eb…71ab

0xea1b8e…c5ec

2 touches
0 conflicts

0x3572bd92…dd29

0xea1b8e…c5ec

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: 0x1b68626d…2de19c

1 conflict on slot 0xcb45d9d62a…b1cb85

← previous block·next block →recent activity