← previous blocknext block →recent activity

Analyzing

Block #75,233,106

10 transactions · 9 stateful · 2026-05-17 18:04:28 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x4f4bdabd…ffba

0x34b655…2a6f

4 touches
1 conflict

0x6caf33e2…c261

0x34b655…2a6f

4 touches
1 conflict

0x96f39b8e…f795

0x34b655…2a6f

4 touches
1 conflict

0x994d36bf…c1ff

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x20261f24…7bc3

0x34b655…2a6f

4 touches
1 conflict

0x4118bd12…924a

0x34b655…2a6f

4 touches
1 conflict

0x00000000…002b

0x1b6862…e19c

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 0x4f4bdabdf3…ecffba

← previous block·next block →recent activity