← previous blocknext block →recent activity

Analyzing

Block #74,430,039

13 transactions · 11 stateful · 2026-05-14 00:38:35 UTC

Parallelism

85/100

Blocked

27%

Avg conflicts / tx

0.31

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,430,039  ·  13 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xd1a0adf6…6e55

0x54cd53…9e7d

2 touches
0 conflicts

0x022548c4…fbcc

0x6657d1…8ccc

2 touches
0 conflicts

0x09330a82…1e8a

0x6657d1…8ccc

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 0x0000000000…00003d

← previous block·next block →recent activity