← previous blocknext block →recent activity

Analyzing

Block #74,978,975

17 transactions · 17 stateful · 2026-05-16 13:47:50 UTC

Parallelism

76/100

Blocked

53%

Avg conflicts / tx

0.82

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,978,975  ·  17 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

0xb9868b52…c77f

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x4197eb3c…51cb

0xd32edf…ff58

5 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x4039b31f…0f4a

0x754704…b603

4 touches
1 conflict

0x6b319071…a105

0xc8689a…ee79

4 touches
1 conflict

0x2691869a…dd4c

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 0xb9868b5233…c6c77f

← previous block·next block →recent activity