← previous blocknext block →recent activity

Analyzing

Block #74,454,729

23 transactions · 18 stateful · 2026-05-14 03:22:59 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,454,729  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1a9

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1aa

0x8d66a4…3095

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x8a35acfb…d1ab

0x8d66a4…3095

5 touches
3 conflicts

0x904fc3c0…00ec

0x34b655…2a6f

4 touches
1 conflict

0xa3ff1ab2…8ae3

0x34b655…2a6f

4 touches
1 conflict

0xc08384da…ecb7

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity