← previous blocknext block →recent activity

Analyzing

Block #74,607,364

21 transactions · 17 stateful · 2026-05-14 20:26:29 UTC

Parallelism

86/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,607,364  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x44102a6e…2ea1

0x34b655…2a6f

4 touches
1 conflict

0xadac4a86…c2bc

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xd7bdb82f…5e44

0x065c9d…c394

3 touches
1 conflict

0x78b7bb99…b926

0x0594c7…a3be

2 touches
0 conflicts

0xb504cd7e…5a81

0x0594c7…a3be

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: 0xab35264b…1cfa38

3 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity