← previous blocknext block →recent activity

Analyzing

Block #74,627,330

16 transactions · 14 stateful · 2026-05-14 22:39:36 UTC

Parallelism

81/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,627,330  ·  16 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

0x4ec9ff52…e6f7

0x34b655…2a6f

4 touches
1 conflict

0xac206e47…ef7d

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0efc210e…70ab

0x34b655…2a6f

4 touches
1 conflict

0x72a152dd…9d0c

0x16f70c…c3dd

2 touches
0 conflicts

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x0eac6378…36f4

0x34b655…2a6f

2 touches
0 conflicts

0x01a89030…f786

0x368ee5…7ca4

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 0x4ec9ff52ce…67e6f7

← previous block·next block →recent activity