← previous blocknext block →recent activity

Analyzing

Block #74,458,811

17 transactions · 11 stateful · 2026-05-14 03:50:11 UTC

Parallelism

88/100

Blocked

9%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,458,811  ·  17 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

0xd40bddc1…773c

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xb245fe36…d765

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x00000000…0004

0x35fa64…a655

2 touches
0 conflicts

0x00000000…0004

0x418541…9c3d

2 touches
0 conflicts

0x00000000…0004

0x43a05b…a68f

2 touches
0 conflicts

0x00000000…0004

0x847a30…d563

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 0xd40bddc144…4e773c

← previous block·next block →recent activity