← previous blocknext block →recent activity

Analyzing

Block #74,650,859

9 transactions · 9 stateful · 2026-05-15 01:16:16 UTC

Parallelism

78/100

Blocked

11%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,650,859  ·  9 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

0x2f7781d6…e632

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x97d5efed…1aa4

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x12fd91b6…cbe3

0x34b655…2a6f

2 touches
0 conflicts

0x742436a7…c4d4

0x34b655…2a6f

2 touches
0 conflicts

0x94710b77…a921

0x34b655…2a6f

2 touches
0 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

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 0x2f7781d6c5…16e632

← previous block·next block →recent activity