← previous blocknext block →recent activity

Analyzing

Block #75,196,642

16 transactions · 14 stateful · 2026-05-17 14:00:56 UTC

Parallelism

75/100

Blocked

29%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,196,642  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x3d34f2bd…5d63

0x34b655…2a6f

4 touches
1 conflict

0x4cd9ba49…83cb

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1539

0x34b655…2a6f

4 touches
1 conflict

0xf8e6479f…f193

0x34b655…2a6f

4 touches
1 conflict

0x23529e13…6f25

0x34b655…2a6f

4 touches
1 conflict

0xfbabb02d…af07

0x34b655…2a6f

4 touches
1 conflict

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity