← previous blocknext block →recent activity

Analyzing

Block #74,968,397

13 transactions · 12 stateful · 2026-05-16 12:37:15 UTC

Parallelism

69/100

Blocked

50%

Avg conflicts / tx

0.92

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,968,397  ·  13 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x631b4113…baa9

0x34b655…2a6f

8 touches
6 conflicts

0x3817764d…242b

0x34b655…2a6f

6 touches
3 conflicts

0xf06c2cf5…61bd

0x34b655…2a6f

6 touches
3 conflicts

0x9c3d5969…a326

0x34b655…2a6f

6 touches
3 conflicts

0xba38536d…2b7d

0x065c9d…c394

6 touches
3 conflicts

0x348fda08…7e96

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x26a96f1d…523f

0x34b655…2a6f

4 touches
1 conflict

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

6 conflicts on slot 0x631b41138f…31baa9

← previous block·next block →recent activity