← previous blocknext block →recent activity

Analyzing

Block #74,353,710

18 transactions · 14 stateful · 2026-05-13 16:10:30 UTC

Parallelism

83/100

Blocked

21%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,353,710  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x2f7781d6…e632

0x34b655…2a6f

6 touches
3 conflicts

0xa2b16f3f…0d71

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0000

0x324719…7534

4 touches
1 conflict

0x801a6e57…d85c

0x34b655…2a6f

4 touches
1 conflict

0x97d5efed…1aa4

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0xe5e7089a…fb91

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity