← previous blocknext block →recent activity

Analyzing

Block #75,469,530

10 transactions · 6 stateful · 2026-05-18 20:25:17 UTC

Parallelism

80/100

Blocked

17%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,469,530  ·  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

0xded5ec0c…f0fc

0x34b655…2a6f

4 touches
1 conflict

0x21d22421…0b7a

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x892daf6e…48d8

0x065c9d…c394

2 touches
0 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

2 touches
0 conflicts

0x0711ec2d…d973

0x34b655…2a6f

2 touches
0 conflicts

0x408e66bb…3d6b

0x34b655…2a6f

2 touches
0 conflicts

0x414e9446…4b59

0x34b655…2a6f

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 0xded5ec0c97…40f0fc

← previous block·next block →recent activity