← previous blocknext block →recent activity

Analyzing

Block #75,105,741

13 transactions · 9 stateful · 2026-05-17 03:54:03 UTC

Parallelism

85/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,105,741  ·  13 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

0x631b4113…baa9

0x34b655…2a6f

4 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x348fda08…7e96

0x065c9d…c394

2 touches
0 conflicts

0x53ce0d98…d61e

0x065c9d…c394

2 touches
0 conflicts

0x60bcb426…ac27

0x065c9d…c394

2 touches
0 conflicts

0x6a7d6552…1f36

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 0x631b41138f…31baa9

← previous block·next block →recent activity