← previous blocknext block →recent activity

Analyzing

Block #74,419,120

13 transactions · 12 stateful · 2026-05-13 23:25:54 UTC

Parallelism

69/100

Blocked

50%

Avg conflicts / tx

0.77

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,419,120  ·  13 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

0x6737ee07…9978

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xeebd31ac…0794

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xf4672ee6…d818

0x34b655…2a6f

4 touches
1 conflict

0xb2ad41aa…b6ca

0x34b655…2a6f

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

6 conflicts on slot 0x6737ee07d3…1e9978

← previous block·next block →recent activity