← previous blocknext block →recent activity

Analyzing

Block #75,506,203

12 transactions · 9 stateful · 2026-05-19 00:35:01 UTC

Parallelism

83/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,506,203  ·  12 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

0xb9868b52…c77f

0x34b655…2a6f

4 touches
1 conflict

0x070a562a…8147

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

2 touches
0 conflicts

0x064b2183…071a

0xea1b8e…c5ec

2 touches
0 conflicts

0x09744403…b936

0xea1b8e…c5ec

2 touches
0 conflicts

0x1c1a981e…f3da

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: 0x34b6552d…112a6f

1 conflict on slot 0xb9868b5233…c6c77f

← previous block·next block →recent activity