← previous blocknext block →recent activity

Analyzing

Block #74,597,361

23 transactions · 21 stateful · 2026-05-14 19:19:13 UTC

Parallelism

74/100

Blocked

38%

Avg conflicts / tx

0.91

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,597,361  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xbad68552…e6bf

0x34b655…2a6f

6 touches
3 conflicts

0xebadaba6…8cc5

0x34b655…2a6f

4 touches
1 conflict

0x1ff9ed6d…37bd

0x34b655…2a6f

4 touches
1 conflict

0x59ef13ba…2741

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0xe5e7089a…fb91

0x34b655…2a6f

4 touches
1 conflict

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

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity