← previous blocknext block →recent activity

Analyzing

Block #74,620,254

13 transactions · 10 stateful · 2026-05-14 21:52:24 UTC

Parallelism

85/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,620,254  ·  13 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

0x0462262d…a368

0x34b655…2a6f

4 touches
1 conflict

0x5b6af007…0f35

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x51087f5a…61f7

0x34b655…2a6f

2 touches
0 conflicts

0x742436a7…c4d4

0x34b655…2a6f

2 touches
0 conflicts

0x83f3d320…fb59

0x34b655…2a6f

2 touches
0 conflicts

0xa6464996…3af9

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 0x0462262d7c…7ea368

← previous block·next block →recent activity