← previous blocknext block →recent activity

Analyzing

Block #74,457,024

17 transactions · 13 stateful · 2026-05-14 03:38:18 UTC

Parallelism

82/100

Blocked

15%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,457,024  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xd40bddc1…773c

0x34b655…2a6f

4 touches
1 conflict

0x1aa8e8ba…8954

0x34b655…2a6f

4 touches
1 conflict

0x1c389468…6b0e

0x34b655…2a6f

4 touches
1 conflict

0xb245fe36…d765

0x34b655…2a6f

4 touches
1 conflict

0xd41f46c4…c0d9

0x0c65a0…0852

2 touches
0 conflicts

0xfb083229…0138

0x2a68ba…90c5

2 touches
0 conflicts

0x5860c4f3…0c39

0x3bd359…433a

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

← previous block·next block →recent activity