← previous blocknext block →recent activity

Analyzing

Block #74,588,460

21 transactions · 13 stateful · 2026-05-14 18:19:37 UTC

Parallelism

86/100

Blocked

38%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,588,460  ·  21 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

0xbb1747e2…f78b

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xca0fef1c…b548

0x34b655…2a6f

6 touches
3 conflicts

0xef77d897…f268

0xd32edf…ff58

5 touches
3 conflicts

0x68b53e57…0091

0x34b655…2a6f

4 touches
1 conflict

0x25bc9a60…6987

0x065c9d…c394

4 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

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

3 conflicts on slot 0xbb1747e217…82f78b

← previous block·next block →recent activity