← previous blocknext block →recent activity

Analyzing

Block #74,429,891

22 transactions · 20 stateful · 2026-05-14 00:37:36 UTC

Parallelism

82/100

Blocked

40%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,429,891  ·  22 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

0x59a54ff4…d21b

0x34b655…2a6f

6 touches
3 conflicts

0xb9d2cf20…a668

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x6f05961b…ecba

0x34b655…2a6f

4 touches
1 conflict

0xb74234b0…12e9

0x34b655…2a6f

4 touches
1 conflict

0xd40bddc1…773c

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

3 conflicts on slot 0x59a54ff481…17d21b

← previous block·next block →recent activity