← previous blocknext block →recent activity

Analyzing

Block #74,587,185

12 transactions · 12 stateful · 2026-05-14 18:11:07 UTC

Parallelism

83/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,587,185  ·  12 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

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0dc352a4…8f3c

0x065c9d…c394

2 touches
0 conflicts

0x8d4bebe2…42f4

0x065c9d…c394

2 touches
0 conflicts

0x3beb3c31…a51f

0x0c65a0…0852

2 touches
0 conflicts

0xaf41644f…8f2e

0x0c65a0…0852

2 touches
0 conflicts

0x046a928e…0012

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: 0x065c9d28…a9c394

1 conflict on slot 0x24968e6db4…f00132

← previous block·next block →recent activity