← previous blocknext block →recent activity

Analyzing

Block #74,555,767

14 transactions · 12 stateful · 2026-05-14 14:40:06 UTC

Parallelism

86/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,555,767  ·  14 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

0x161db613…d254

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x5e1c23e9…4f81

0x34b655…2a6f

4 touches
1 conflict

0x206f4379…e08a

0x34b655…2a6f

4 touches
1 conflict

0x18b11fba…c92a

0x34b655…2a6f

4 touches
1 conflict

0xd621be95…e5af

0xd32edf…ff58

3 touches
1 conflict

0x00000000…0003

0x139aab…382b

2 touches
0 conflicts

0x00000000…0001

0x139aab…382b

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 0x161db613a2…63d254

← previous block·next block →recent activity