← previous blocknext block →recent activity

Analyzing

Block #74,563,144

17 transactions · 14 stateful · 2026-05-14 15:30:04 UTC

Parallelism

76/100

Blocked

29%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,563,144  ·  17 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

0x6713b018…05f3

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xee576a92…fe14

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x1348a4c0…8d19

0x34b655…2a6f

2 touches
0 conflicts

0x60a42a5e…9da2

0x34b655…2a6f

2 touches
0 conflicts

0x71e4ffd1…9beb

0x34b655…2a6f

2 touches
0 conflicts

0xc824469a…641d

0x34b655…2a6f

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

3 conflicts on slot 0x6713b0185b…1305f3

← previous block·next block →recent activity