← previous blocknext block →recent activity

Analyzing

Block #74,492,214

15 transactions · 12 stateful · 2026-05-14 07:32:26 UTC

Parallelism

80/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,492,214  ·  15 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

0x83f3d320…fb59

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x7d0eaae2…60b7

0x34b655…2a6f

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

2 touches
0 conflicts

0x7b43f938…3650

0x000000…012a

2 touches
0 conflicts

0x294fb37b…40d3

0x188d58…ea8e

2 touches
0 conflicts

0x294fb37b…40d4

0x188d58…ea8e

2 touches
0 conflicts

0x4dd1db39…a994

0x188d58…ea8e

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 0x83f3d32000…25fb59

← previous block·next block →recent activity