← previous blocknext block →recent activity

Analyzing

Block #74,460,162

16 transactions · 11 stateful · 2026-05-14 03:59:11 UTC

Parallelism

88/100

Blocked

18%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,460,162  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0xac2a0273…7212

0x34b655…2a6f

4 touches
1 conflict

0x064a3cb8…c43e

0x09475a…400f

2 touches
0 conflicts

0xd420023a…cf6a

0x09475a…400f

2 touches
0 conflicts

0x00000000…0002

0xab3526…fa38

2 touches
0 conflicts

0x34e65d5c…838e

0xd5d960…eaee

2 touches
0 conflicts

0x541a74a9…d0c2

0xd5d960…eaee

2 touches
0 conflicts

0x88ef4191…6de8

0xd5d960…eaee

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: 0x34b6552d…112a6f

1 conflict on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity