← previous blocknext block →recent activity

Analyzing

Block #74,420,689

20 transactions · 14 stateful · 2026-05-13 23:36:18 UTC

Parallelism

80/100

Blocked

29%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,420,689  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x35e0a15d…49d6

0xd32edf…ff58

7 touches
6 conflicts

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 conflicts

0x6d3780e3…0829

0x34b655…2a6f

2 touches
0 conflicts

0x8b8e4020…11b0

0x34b655…2a6f

2 touches
0 conflicts

0x904fc3c0…00ec

0x34b655…2a6f

2 touches
0 conflicts

0xa3ff1ab2…8ae3

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: 0xd32edf66…9fff58

6 conflicts on slot 0x35e0a15df3…d349d6

← previous block·next block →recent activity