← previous blocknext block →recent activity

Analyzing

Block #75,468,370

17 transactions · 15 stateful · 2026-05-18 20:17:33 UTC

Parallelism

71/100

Blocked

27%

Avg conflicts / tx

0.59

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,468,370  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x37d49489…9309

0x34b655…2a6f

6 touches
3 conflicts

0x19710e1a…212d

0x34b655…2a6f

4 touches
1 conflict

0x386d08f4…5a01

0x34b655…2a6f

4 touches
1 conflict

0x537e2e5b…c3ab

0x34b655…2a6f

4 touches
1 conflict

0x5b6af007…0f35

0x34b655…2a6f

4 touches
1 conflict

0x5d70606a…1d53

0x34b655…2a6f

4 touches
1 conflict

0x81e1f4e8…08d7

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity