← previous blocknext block →recent activity

Analyzing

Block #74,465,578

23 transactions · 9 stateful · 2026-05-14 04:35:14 UTC

Parallelism

91/100

Blocked

11%

Avg conflicts / tx

0.04

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,465,578  ·  23 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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x59a54ff4…d21b

0x34b655…2a6f

4 touches
1 conflict

0x7cee1be1…e770

0x34b655…2a6f

4 touches
1 conflict

0x8cc18498…ce7e

0x34b655…2a6f

3 touches
1 conflict

0xded46462…1ec7

0x065c9d…c394

2 touches
0 conflicts

0x3f1434d4…1ce1

0x11ed3b…2c96

2 touches
0 conflicts

0x046a928e…0012

0x2a68ba…90c5

2 touches
0 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity