← previous blocknext block →recent activity

Analyzing

Block #74,369,014

13 transactions · 10 stateful · 2026-05-13 17:52:20 UTC

Parallelism

77/100

Blocked

20%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,369,014  ·  13 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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x14244448…ccb5

0x34b655…2a6f

2 touches
0 conflicts

0x478d93a8…24d7

0x34b655…2a6f

2 touches
0 conflicts

0x52f2f7aa…0dc9

0x34b655…2a6f

2 touches
0 conflicts

0x6737ee07…9978

0x34b655…2a6f

2 touches
0 conflicts

0x94710b77…a921

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: 0x2a68ba18…8e90c5

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity