← previous blocknext block →recent activity

Analyzing

Block #74,415,558

15 transactions · 11 stateful · 2026-05-13 23:02:12 UTC

Parallelism

87/100

Blocked

27%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,415,558  ·  15 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

0x00000000…0000

0x6c1852…e838

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x64c4114a…fd48

0x065c9d…c394

2 touches
0 conflicts

0x8e67e4fe…e414

0x065c9d…c394

2 touches
0 conflicts

0xa037f18f…a3b9

0x065c9d…c394

2 touches
0 conflicts

0xcd53e2c7…fe6e

0x065c9d…c394

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: 0x6c1852bc…83e838

1 conflict on slot 0x0000000000…000000

← previous block·next block →recent activity