← previous blocknext block →recent activity

Analyzing

Block #74,356,187

17 transactions · 14 stateful · 2026-05-13 16:27:01 UTC

Parallelism

88/100

Blocked

21%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,356,187  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x8c49c85c…ee96

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0000

0x870f91…3b8e

4 touches
1 conflict

0x0d3588f0…8e78

0x065c9d…c394

3 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x6ccce044…73e2

0x065c9d…c394

2 touches
0 conflicts

0x7ee98917…bdcc

0x065c9d…c394

2 touches
0 conflicts

0xdadeb30c…7943

0x065c9d…c394

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